-
Notifications
You must be signed in to change notification settings - Fork 54
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
chore: Prepare for sunset icon removal from core #63
chore: Prepare for sunset icon removal from core #63
Conversation
Cool can do that. PR looks good too |
I am stuck though making a new release because the pom.xml has to be changed according to this format: Does anyone know if there is some script that would update this? |
The pom looks good, you have a parent set and a properties tag for the plugin baseline. Though to note, I'm more used to releasing via CD and incrementals. |
I am getting this when I try to release, if you have any insight, I am not that exprneinced in this 😊 Ran:
got:
|
Did you change <version>${revision}${changelist}</version>
<tag>${scmTag}</tag> to <version>1.53</version>
<tag>1.53</tag> ? |
Ok that works, but I can't push stuff to http://repo.jenkins-ci.org/public/ now, nor can I reset my password (user has no permissions to reset password) :-/
|
Hm weird, I changed to deploying via CD considering I find it more convenient, but according to the RPU you have permission. |
not sure from a quick look |
@NotMyFault How do you use CD to release? |
Where does that go?
|
File a PR against the RPU for your |
It's automatically done by RPU when cd.enabled = true is set |
Preparation for core sunsetting dated icons:
https://github.com/jenkinsci/jenkins/pull/5778
@guysoft Would be nice if you can also trigger a release after merging this PR. The core PR is blocked until then.
Thanks in advance!