[DevOps World Jenkins World Nice]: Volunteers needed

Hello, I'm looking for volunteers to help staff the Ask the Expert booth at DevOps World Jenkins World Nice . Staffing hours needed are as follows: - Tuesday, Oct 23 @ 5pm - 7pm - Wednesday, Oct 24 during breaks, lunch, and reception -

Re: Jenkins in Hacktoberfest 2018?

I can help review Chinese localization pr. Thanks Oleg. On Tue, Oct 2, 2018 at 8:27 AM R. Tyler Croy wrote: > (replies inline) > > On Mon, 01 Oct 2018, Oleg Nenashev wrote: > > > Hi all, > > > > We are live: https://jenkins.io/blog/2018/10/01/hacktoberfest/ > > Let the hacking commence! > > >

Re: Jenkins in Hacktoberfest 2018?

(replies inline) On Mon, 01 Oct 2018, Oleg Nenashev wrote: > Hi all, > > We are live: https://jenkins.io/blog/2018/10/01/hacktoberfest/ > Let the hacking commence! Excellent work! Thanks for leading the charge Oleg, I'm looking forward to some fun hacking from everybody this month :) --

Wiki plugin labels

I maintain the HockeyApp plugin and was curious as to why the *android* label does not appear on the plugin page nor on the Android filter on the plugin index . I used the Jenkins plugin API for my plugin and

Re: Jenkins in Hacktoberfest 2018?

Hi all, We are live: https://jenkins.io/blog/2018/10/01/hacktoberfest/ Let the hacking commence! Just in case, we have Hacktoberfest assist teams in GitHub: - @jenkinsci/hacktoberfest - @jenkins-infra/hacktoberfest

[Contributor Summit Nice]: Jenkins Evergreen delivery

Hi Tyler/Baptiste, With the Jenkins Contributor Summit Nice approaching in a few weeks, I wanted to follow up to see who do you suggest to 1) deliver the Jenkins Evergreen status update presentation 2) lead the Jenkins Evergreen BoF table discussion? Thanks, alyssa -- You received this message

Re: Bad release

Thank you. That was exactly what I was looking for. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view

Re: Bad release

Look for "Rename a class" on https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility it will show how to use XStream aliases. On Mon, Oct 1, 2018 at 7:24 AM pallen wrote: > I renamed my MultiBranch classes from *ScmSource to *SCMSource forgetting > the impact on the XML

Re: Looking to join maintainership of ec2-plugin

Awesome, thanks! On Sat, Sep 29, 2018 at 7:15 AM Baptiste Mathus wrote: > @Matt thanks for the offer. As per the approval of Fabrizio, I've just > added you as a committer. > > As usual, remember this ^ is only for commit / merge access. If you wish > to be able to release, you'll want to go

Re: Bad release

I renamed my MultiBranch classes from *ScmSource to *SCMSource forgetting the impact on the XML configuration data. I could undo the rename, or better find a way to read the old XML configuration data? -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Bad release

Just release a new version? On Mon, Oct 1, 2018 at 10:19 PM Jesse Glick wrote: > On Mon, Oct 1, 2018 at 8:20 AM pallen wrote: > > How do I remove a bad release from the Update Centre! > > If it is already in the hands of users, I think you need to “fix forward”. > > -- > You received this

Re: jep/213 "Configuration Storage API" vs SideCar

BTW could you move this thread to jenkins-cloud-native-...@googlegroups.com which is probably the right forum? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: Bad release

On Mon, Oct 1, 2018 at 8:20 AM pallen wrote: > How do I remove a bad release from the Update Centre! If it is already in the hands of users, I think you need to “fix forward”. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Bad release

Thank you. Yes, I am the plugin owner. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this

Re: Bad release

You could add an item into here https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/artifact-ignores.properties if you are the owner of the plugin. On Mon, Oct 1, 2018 at 8:20 PM pallen wrote: > Hi Guys, > > How do I remove a bad release from the Update Centre! > >

Re: jep/213 "Configuration Storage API" vs SideCar

On Mon, Oct 1, 2018 at 6:51 AM nicolas de loof wrote: > we just don't need to wait for a new jenkins-core release, this can be > adopted without delay. If I understand your proposal correctly, you suggest that a sidecar container fetch cloud-native configuration (say, K8S CRDs) as an

Re: Jenkins Localization Separation discuss

On Sat, Sep 29, 2018 at 10:38 PM Rick wrote: > detect browse user-agent setting As far as I know this is how locale is normally taken into account in Jenkins, so this proposal makes sense to me. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Proposal: Experimental Docker images and CD for Jenkins master/stable branches

On Sat, Sep 29, 2018 at 1:02 PM Oleg Nenashev wrote: > Build happens before ci.jenkins.io completes the build/test cycle Does not seem like a serious issue. It is marked experimental after all, and we assume that commits in `master` are nothing more than merges of PRs which were already tested.

Bad release

Hi Guys, How do I remove a bad release from the Update Centre! p4-plugin 1.9.0 Looks like a case-sensitivity Class Name refactor has messed up the Jenkins XML configuration. Any tips on that too? or just reinstate the old class name? Kind regards, Paul -- You received this message

jep/213 "Configuration Storage API" vs SideCar

Hi, I've read JEP-213 proposal with lots of interest, IIUC there's no plan to change the configuration granularity (we still will have one configuration entry per legacy xml file) neither do we plan to change the data being