Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LTS Track for Jenkins Snap #88

Open
wants to merge 4 commits into
base: lts
Choose a base branch
from

Conversation

kz6fittycent
Copy link
Contributor

In response to #81

@kz6fittycent kz6fittycent changed the title Lts LTS Track for Jenkins Snap May 13, 2024
Copy link
Member

@jnsgruk jnsgruk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little unclear on the intention here -- are you looking to replace the candidate track with an lts track, or run both at the same time?

.github/workflows/release-to-candidate.yml Outdated Show resolved Hide resolved
changed to `snapcrafters/ci/release-to-candidate@main`
Comment on lines 14 to 27
jobs:
sync:
name: 🔄 Sync version with upstream
environment: "Candidate Branch"
environment: "LTS Branch"
runs-on: ubuntu-latest
steps:
- name: 🔄 Sync version with upstream
uses: snapcrafters/ci/sync-version@main
with:
token: ${{ secrets.SNAPCRAFTERS_BOT_COMMIT }}
update-script: |
# Grabbing latest release
VERSION=$(curl -sL https://api.github.com/repos/jenkinsci/jenkins/releases | jq .[].tag_name -r | grep -v rc | sort -r | head -n 1 | cut -d "-" -f2)
# Grabbing latest lts release
VERSION=$(curl -sL https://api.github.com/repos/jenkinsci/jenkins/releases | jq .[].tag_name -r | grep -v rc | sort -r | grep "2.440" | head -n1 | cut -d "-" -f2)
sed -i 's/^\(version: \).*$/\1'"'$VERSION'"'/' snap/snapcraft.yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file can be removed, and you'll need to add another stanza to the update script on the candidate branch, because scheduled workflows only run on the default branch. See sublime-text or sublime-merge for an example :)

Comment on lines 11 to 17
jobs:
promote:
name: ⬆️ Promote to stable
environment: "Candidate Branch"
environment: "LTS Branch"
runs-on: ubuntu-latest
if: |
( !github.event.issue.pull_request )
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file can also be removed, you'll need to delete this on this branch, then update the promotion workflow on candidate

@@ -46,7 +46,7 @@ jobs:
call-for-testing:
name: 📣 Create call for testing
needs: [release, get-architectures]
environment: "Candidate Branch"
environment: "LTS Branch"
runs-on: ubuntu-latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jnsgruk
Copy link
Member

jnsgruk commented Jun 1, 2024

A few more comments now I understand better - thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants