Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using Environments without creating deployment automatically

See original GitHub issue

Current Situation: Every pipeline step that uses environments automatically creates a new deployment. This seems to be wanted behavior.

Problem Access to an environment might be also needed for other reasons than deployments. Like running integration tests (deployment already done; we want to assure correct behavior of latest deployment)

Possible Solution Can we add an option to avoid an automatic deployment always when using environment? An idea might be to set an environment variable like AUTO_DEPLOYMENT=false.

Additional information

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:115
  • Comments:23

github_iconTop GitHub Comments

yusijscommented, Jan 23, 2023

This would be great, my pull requests currently look like this: image

We use environments for builds etc as well (secrets), so it becomes a mess very quickly. Being able to specify the environment at the top level (before the jobs) might also help a bit, but ideally it would be possible to do something like this in the job definition:

  name: dev
  deployment: false
floberndcommented, Sep 14, 2022

The exact same thing bugs me as well.

I would even go one step further and decouple the deployments from environments completely by default.

Imho every workflow should be able to be a deployment task - or not. Instead of using the environment to determine this, we could just have another string key in the yaml (similar to the “concurrency” key).

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to use environments when used for secrets for ...
Hi,. we are using GitHub Actions environments for both, to store env-specific secrets, and to integrate manual approval on deployment-jobs.
Read more >
Environments and deployments | GitLab
Tutorial: Use GitLab to run an Agile iteration · Milestones · Burndown and burnup charts · Issues · Create issues · Manage issues...
Read more >
Environments are not automatically created in Azure ...
1 Answer 1 · You use the YAML pipeline creation wizard in the Azure Pipelines web experience and refer to an environment that...
Read more >
EVERYTHING you NEED to know about GitHub Actions ...
Deploy to Production only after Staging, with an Approval. To do this, you would need first to create three environments, add the approvers...
Read more >
Create target environment - Azure Pipelines
An environment is a collection of resources that you can target with deployments from a pipeline. Typical examples of environment names are Dev, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found