You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Contributing.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
- Check that someone listed as _submitter_ in Jenkinsfile is available
4
4
- Create a tag and push it
5
-
- Start build [on Jenkins CI](https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/VS%20Code/job/vscode-apache-camel-extension-pack-release/) with _publishToMarketPlace_ parameter checked
5
+
- Start build [on Jenkins CI](https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.com/job/Fuse/job/VSCode/job/vscode-camel-lsp-extension-pack-release/) with _publishToMarketPlace_ parameter checked
6
6
- Wait the build is waiting on step _Publish to Marketplace_
7
7
- The vsix is downloadable and can be tested a last time before publishing it to public
8
8
- Ensure you are logged in
9
9
- Go to the console log of the build and click "Proceed"
10
10
- Wait few minutes and check that it has been published on [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack)
11
11
- Keep build forever for later reference and edit build information to indicate the version
12
-
- Update package.json and Changelog.md with next version to prepare for new iteration release (via a Pull Request)
12
+
- Update package.json and Changelog.md with next version to prepare for new iteration release (via a Pull Request)
0 commit comments