Autorun on deployment

Topic Labels: Automations
209 2
Showing results for 
Search instead for 
Did you mean: 
5 - Automation Enthusiast
5 - Automation Enthusiast

Hello, for the last few days we noticed that our scheduled per-day automations run on each Update (when we edit scripts and Update automation)

Is it expected new behavior?

2 Replies 2
4 - Data Explorer
4 - Data Explorer


  • Choose the Right CI/CD Tool: Select a continuous integration and continuous deployment (CI/CD) tool that supports autorun functionality. Popular options include Jenkins, GitLab CI/CD, and GitHub Actions.

  • Configure Your Repository: Ensure your code repository is properly configured with the necessary files and structure. This includes having a Dockerfile, docker-compose.yml, or equivalent for your application.

  • Define Your Pipeline: Create a pipeline configuration file (e.g., .gitlab-ci.yml, .github/workflows/main.yml) in your repository. This file will outline the stages and jobs for your deployment process.

  • Set Up Environment Variables: Define any environment variables needed for your deployment. These can be stored securely in your CI/CD tool’s settings.

  • Create Deployment Scripts: Write deployment scripts that will be executed during the deployment process. These scripts should include commands to build, test, and deploy your application.

  • Include SEO Best Practices: Ensure your deployment process includes steps for seo optimization. This can involve generating sitemaps, updating meta tags, and ensuring your site’s content is search engine friendly.

  • Test Automation: Incorporate automated tests in your deployment pipeline. This includes unit tests, integration tests, and seo audits to ensure your application meets quality and SEO standards.

  • Build and Push Docker Image: If using Docker, include steps in your pipeline to build and push the Docker image to a container registry. This ensures your application is packaged and ready for deployment.

  • Deploy to Staging Environment: Configure your pipeline to deploy the application to a staging environment first. This allows for testing and validation before going live.

  • Run SEO Audits: After deploying to the staging environment, run SEO audits using tools like Lighthouse or SEO-specific scripts to check for SEO issues and opportunities.


5 - Automation Enthusiast
5 - Automation Enthusiast

Pardon? I'm afraid I cannot understand how it relates to my question