DevOps Stack Exchange
DevOps Stack Exchange

Questions tagged [release]

A release or releasing is the act of making features or bug fixes available for consumption. A release is not necessarily the same as a deployment, with the latter being the promotion of code into an environment, feature flags or toggles may be used to hide new functionality from consumers.

"A release" or simply releasing is the act of making features or bug fixes available for consumption. A release is not necessarily the same as a deployment, with the latter being the promotion of code into an environment, feature flags or toggles may be used to hide new functionality from consumers.

Further Reading

Other mechanism for splitting release from deployment:

Related Tags:

23 questions
11
votes
2 answers

Is it possible to autodeploy on every commit in a specific branch using Travis CI and GitHub?

I'd like to deploy files using Travis CI and it only works for a tagged commit. When committing to the branch, there is a warning: Skipping a deployment with the releases provider because this is not a tagged commit. Is there any way to deploy on…
kenorb
  • 8,011
  • 14
  • 43
  • 80
10
votes
2 answers

How to avoid branchageddon with large organisations?

How do you avoid a branchageddon situation when working with large organisations? We work with a number of large financial organisations whose approach is to not take updates to software, but instead only high/critical security patches and bespoke…
Mark Wheeler
  • 103
  • 4
8
votes
2 answers

What is the difference between packages and artifacts?

I would like to understand the difference between package and artifact. Also In what context we should use these terms.
Shash
  • 183
  • 1
  • 6
6
votes
2 answers

How to decide between Rolling Releases versus LTS Releases?

There are software packages that offer a choice between either of those types of releases: a Rolling release. a Long Term Support (= LTS) release. Consider the available Ubuntu releases as an example of this. And imagine that: some software…
Pierre.Vriens
  • 7,225
  • 14
  • 39
  • 84
5
votes
1 answer

What is difference between release and deployment?

What is the basic difference between software release and deploy? What is the relation between software release management and continuous deployment?
rohit.dagur
  • 51
  • 1
  • 2
5
votes
5 answers

How to correlate Devops deploy on demand with Agile Sprint Process

I'm not clear how a Sprint which is timed-box to a predetermined length (1/2/3 weeks) fits with a DevOps principle of being able to deploy on demand or as needed. Is deploying to production part of the definition of done rather than a post activity…
Beaux
  • 51
  • 3
4
votes
2 answers

RPM's, VM's : time consuming

I am constantly delivering RPM packages upon every new version of some project. Every version is dependent on some developing prerequisites CentOS 7 git Some npm packages. Some Python PIP packages Some shared objects I'm dealing with this issue…
Amit Arie
  • 41
  • 1
3
votes
1 answer

Best practice for building releases with Jenkins multibranch pipeline

We have started moving from Subversion to git (using Bitbucket, to be exact), and I'm unsure how to manage release builds with the multibranch concept. This is how we do it in Subversion: We have one Jenkins job based on a declarative pipeline…
not2savvy
  • 131
  • 1
  • 5
3
votes
2 answers

Release/file sharing service

At my company we use FTP to share releases and e-mail to notify customers of the availability. I'm looking for a service offering: Easily upload of a file Users need to sign in to download and keep a record of which user have downloaded…
André Moreira
  • 133
  • 4
3
votes
1 answer

When to "npm publish" when using git flow

I'm using the following resources as a guide to git flow: git-flow cheatsheet git-flow Using git-flow to automate your git branching workflow However, none of them explicitly mention at what point you perform the npm publish from. Do you do this…
Plastikfan
  • 143
  • 4
2
votes
2 answers

Git Release branching strategy for Continuous integration and deployment

We have tried multiple branching strategies to adopt CI/CD. Developers develop on the feature branch and then merging to master which get deployed to QA for testing and then master is deployed to production, so in short whatever goes out to QA/UAT…
Zanky
  • 21
  • 3
2
votes
1 answer

Relation of devops with release management

How does DevOps deal with release management? Is release management is the part of devops lifecycle? Do devops take active part in release management or the organization has hire to another professional altogether.
Abhishek Gurjar
  • 149
  • 6
2
votes
2 answers

Where should I store my build configuration files?

At my work we use git for our source control, MSBuild for our builds, and Jenkins for our CI. Our git repo will have different branches for the cycle of the product (develop, QA, release). My question is where should I store the msbuild xml? If I…
nichos
  • 33
  • 4
2
votes
1 answer

Why should I tag a commit to create a release?

I work on a new CICD, replacing Jenkins-X 2 by GitHub Actions. After seeing a lot of actions to create a release + changelog, I found that a lot of them are trigger by a tag on a commit to launch the workflow. For now, I create a new release on…
benCat
  • 71
  • 1
  • 6
1
vote
1 answer

How trigger a build by a commit in a branch prefix?

On the Azure DevOps, in we git we have a schema of branches where we create a branch per sprint, for sample: sprint01 sprint02 sprint03 ... We keep the 3 last sprint branches, and in this case when I create the sprint4 branch, we will drop the…
Felipe Oriani
  • 115
  • 5
1
2