Comments (6)
amund7
commented on June 28, 2024
1
I like option 2. Then we can also probably get an overview over which commits has happened since last time, and can make a changelog.
I'll try to make the build automation only build a branch we call 'release'.
from canbus-analyzer.
Bokonon79
commented on June 28, 2024
I think you've got the right idea that we need to have separate "dev" and "release" branches, because right now, "master" is effectively serving as both.
I don't have any experience with Azure DevOps, but I am assuming that build/deploy automation can be configured on a per-branch basis, and is currently configured for the master branch. If so, a couple of options might be:
Option 1: Make "master" the release branch. Create a new "develop" or "Latest" branch for the project, and merge all PRs and other changes into this branch. When this branch is confirmed stable and ready for release, merge to "master", triggering the build/deploy automation.
Option 2: Make a new "release" branch, enable build/deploy automation on this branch, and disable that automation on "master". Continue to use "master" as the main "development" branch, merging all PRs and changes there. When "master" is confirmed stable and ready for release, merge to "release", triggering the build/deploy automation.
from canbus-analyzer.
amund7
commented on June 28, 2024
On second thought, I really like that we have super fast, always latest builds. In the event we break something, we can always delete that release manually. I think I'd like to keep it this way for a while and see how it goes.
from canbus-analyzer.
scottstout
commented on June 28, 2024
You can set it to only trigger the release on certain branches and/or
commits with certain tags. Or you can do test relase that goes one place
(e. G . More private)and only when ready you trigger the production release
when you are ready (by setting approvers).
Scott
On Sun, Jan 6, 2019 at 4:40 PM amund7 ***@***.***> wrote:
On second thought, I really like that we have super fast, always latest
builds. In the event we break something, we can always delete that release
manually. I think I'd like to keep it this way for a while and see how it
goes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAICblmTQ3NVnnvBl8Gou3W1XPDnMtPrks5vAntugaJpZM4ZyEx->
.
--
Scott Stout
mobile (713) 320-4376
from canbus-analyzer.
brian-man
commented on June 28, 2024
Recommendation:
- Create a release branch
- Adjust configuration so that master and release branches both automatically generate and publish builds with each commit
- General public uses release branch builds and early adopters can use master branch builds with the expectation that stability isn't the priority for master branch builds
from canbus-analyzer.
amund7
commented on June 28, 2024
Agreed, but the problem is, how to distinguish those builds here on Github? Tags maybe?
As it sits today, the microsoft server builds, creates installer, packages, zips AND uploads the files to github, all automatically.
Or, would it be better to deploy to microsoft 'blob', if that has become free now?
If this could be combined with auto updates (that requires a steady URL from which the installer can be found), that would be a big improvement, which solves #23
from canbus-analyzer.
Related Issues (15)
- a screenshot wanted HOT 5
- CanOPEN import filter broken by known packets definitions HOT 3
- Add support for importing Vector ASCII format
- NotifyPropertyChanged in ListItem throws NullPointerException a lot HOT 4
- Integrate CANTools Log File Readers HOT 8
- Choose which packet definitions to use (Model S, Model 3, Model S DBC, etc.) HOT 3
- Reset packet counts, graphs, etc. when a new file is loaded HOT 1
- Clickonce installer auto-update
- Better playback controls HOT 1
- Improve or rethink "Interpret as", "copy ID" functionality
- Vector ASCII Format: message IDs < 0x100 should be zero-padded
- Multiplexed DBC message implementation has some (poor) assumptions
- Time axis on X axis of graph
- Crash when loading a dbc file HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from canbus-analyzer.