8
votes
Accepted
Release/file sharing service
What you're after is an Binary repository manager
Quoting from Wikipedia with added links:
Notable Universal package managers include:[6]
Apache Archiva
Jfrog's Artifactory
Inedo's ...
7
votes
Accepted
What is the difference between packages and artifacts?
Mainly an artifact is the result of of a build phase, this mean a package is an artifact of a kind.
A package is usually a way to install a software or application, it includes the software itself ...
6
votes
How to correlate Devops deploy on demand with Agile Sprint Process
There is no "Deploy-once-a-day" rule in devops philosophy. It's more of: Deploy as soon as possible and as often as possible. Also it calls for decoupling architecture so different parts of it may be ...
6
votes
Accepted
How to decide between Rolling Releases versus LTS Releases?
I don't think there's a good answer that applies to all software packages or situations.
Rolling releases are more risky as there is no predictability around when things will change. You may have ...
6
votes
Is it possible to autodeploy on every commit in a specific branch using Travis CI and GitHub?
Instead of using Travis' deployment features, build the deployment logic in to your normal "test" script(s). For a PaaS this might be as simple as pushing to another git remote if all tests pass, but ...
5
votes
Relation of devops with release management
Your use of the term "devops" suggests that you see it as a role. I humbly suggest that developers that are part of a Scrum team aren't called "Agiles," so DevOps practitioners aren't "devops." :)
...
4
votes
Accepted
Is it possible to autodeploy on every commit in a specific branch using Travis CI and GitHub?
Travis CI supports deployment on branch release by using the following syntax:
deploy:
on:
branch: release
The problem is that GitHub does not support it.
As per GitHub Releases Uploading ...
4
votes
Accepted
When to "npm publish" when using git flow
I'd set up my CI system to do this on every commit to master, that is, after the release branch merges.
The first very straightforward reason for this is that the commit to master gets tagged with ...
4
votes
Git Release branching strategy for Continuous integration and deployment
You need to separate the 2 concepts a bit:
the integration part - how are the changes integrated into your master branch (or some other integration branch, that's also possible), which may be ...
3
votes
Accepted
How to avoid branchageddon with large organisations?
As Michael mentioned, offer a standard solution based on release versions/numbers, with a reasonably long lifespan for your industry (maybe interleaved with one or more shorter lifespan intermediate ...
3
votes
Release/file sharing service
In DevOps, it is not always about just piciking the right tool, but understanding what is happening also in terms of the workflow.
Interesting aspects are here delivered value (like saved time) and ...
3
votes
What is difference between release and deployment?
From Wikipedia:
Release management is the process of managing, planning, scheduling
and controlling a software build through different stages and
environments; including testing and deploying ...
2
votes
How to correlate Devops deploy on demand with Agile Sprint Process
Some great answers here, but I thought I'd chime in with an example of how we deliver features. "shipping" to production is not the goal, the goal is to deliver value. Shipping code to production is a ...
2
votes
How to correlate Devops deploy on demand with Agile Sprint Process
The Agile software development method
describes a set of values and principles for software development under which requirements and solutions evolve through the collaborative effort of self-...
2
votes
How to correlate Devops deploy on demand with Agile Sprint Process
In a sense your question exactly underlines the problem faced by teams trying to be agile but without having the benefits of a good DevOps culture in place: there is practically no guarantee that at ...
2
votes
RPM's, VM's : time consuming
For a laptop, desktop or standalone server, consider trying out Docker containers. These containers are designed to allow you to provide differing libraries, packages and shared objects uniquely to ...
2
votes
RPM's, VM's : time consuming
Have you considered setting up a build server (i.e. Jenkins, TeamCity) with disposable build agents?
If you do it in the cloud (i.e. via ec2 integration), you can literally set up an AMI with generic ...
1
vote
Should I use release branch to push my changes?
What is the recommended practice?
The book ”Accelerate” by Forsgen, Humble and Kim documents their research that teams that use fewer long-lived branches are more successful.
The question is then ...
1
vote
Best practice for building releases with Jenkins multibranch pipeline
Some of the best practices I have used in the past for building releases with Jenkins multibranch pipelines and Git:
It is recommended to use a release branch for building and deploying release ...
1
vote
Accepted
What permission is required to deploy release?
Found it!
The permissions are set on each release pipeline itself:
"Manage Deployments" allows users to come in and deploy to their environment without allowing them to edit the pipeline.
1
vote
Why should I tag a commit to create a release?
A changelog is handy as one will see what changes reside in a certain release. A couple of months ago one of my tools was not working anymore. By consulting the Changelog it was possible to find the ...
1
vote
Accepted
Azure Release Pipeline Fails Using Expand-Archive Command
This was answered via StackOverflow by Kevin Lu:
https://stackoverflow.com/a/66739852/1224614
In short, the second suggestion he made to update to PowerShell 7 and adding the environment information ...
1
vote
GUI over GitLab CI Environment Deployments With Multiple Instances?
Check out the GitLab Operations Dashboard feature (https://docs.gitlab.com/ee/user/operations_dashboard/)
There is a screenshot on that page, too, so you can get an idea of it.
1
vote
Where Azure DevOps Services Enviromnent come into play?
You need to enable the multi-stage pipelines preview feature. Here is a guide to enable preview features.
1
vote
Accepted
Organizing the build steps on AzureDevOps
You can separate the steps, especially as it would let you do divide the work among different agents. You can also leave them in a single agent if you wish.
The primary advantage I see is leveraging ...
1
vote
How to avoid branchageddon with large organisations?
Maybe if you maintained branches per versions instead of per customers it could help reduce their number?
Otherwise the only way to really get away from it is to be able to host the software yourself ...
1
vote
Where should I store my build configuration files?
Normally the build configuration needs to stay consistent with the product code, so it should be stored into the same git repo as the product code.
It's true, the file would get merged when a branch ...
1
vote
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.
As usual, there is no commonly ...
1
vote
How to decide between Rolling Releases versus LTS Releases?
A rolling release is newer, with cutting-edge functionality, but potentially more defects. LTS is more stable. If stability is your priority (as it generally is for DevOps), LTS would be the release ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
release × 23release-management × 9
git × 5
deployment × 5
azure-pipelines × 4
azure-devops × 3
continuous-deployment × 3
terminology × 2
build-pipeline × 2
builds × 2
artifacts × 2
process × 2
branch × 2
jenkins × 1
jenkins-pipeline × 1
continuous-integration × 1
gitlab × 1
azure × 1
windows × 1
culture × 1
cicd × 1
github × 1
travis-ci × 1
environments × 1
agile × 1