Is it possible to configure job at https://jenkins.ci.cloudbees.com/job/plugins/ to use java 8?

Hi, Our plugin declare java 8 in pom and uses java 8 in source. But the auto created job at https://jenkins.ci.cloudbees.com/job/plugins/ is running/using java 7: Java version: 1.7.0_79, vendor: Oracle Corporation Java home: /opt/java/sdk/Oracle/x86_64/jdk1.7.0_79/jre So it failed the

Re: Translation management plugin

Hi, take a look at http://zanata.org/ (Opensource translation management platform used by Fedora, Openstack community and Red Hat internally) We are developing a Jenkins plugin https://github.com/jenkinsci/zanata-plugin right now (Please wait until pull request 3 is merged or just use that

Re: Jenkins developers who are also IntelliJ users, please all pile on this bug

Intellij users let's make jenkins integration! I'm more confused with IDEA APIs, than cloud apis. 2016.3 fails too much so i'm using 2016.2 and have no issues ;) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: disk-usage-plugin seems to be abandoned

Confirm. @lvotypko made refactorings and disappeared. I made few attempts to request release with fixes in last half year, but nobody from RedHat made release. Plugin is very useful and before lvotypko i was even ready to refactor or write new. Who remember @ogondza email? Please CC him. --

Re: Project ideas for student projects in the area of testing

I'm think that a Jenkins job which asserts the conditions related to a bug report is a regression test. I admit that the Jenkins jobs I create are not Selenium tests, and they do not require a web browser in order to run. They are definitely not able to exercise JavaScript, and they do not

disk-usage-plugin seems to be abandoned

Hi, It seems like the disk-usage-plugin has been abandoned. Last commit is from Feb 10, 2016, last release was done October 1, 2015. The current maintainer lvotypko did not react to messages and

ATH under Windows

Is someone running the acceptance test harness under Windows? The last time I tried it did not work, but this was several months ago. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: plugin data migration - potential incompatibility

I would prefer to do a 1:N transformation, so ItemListener.onLoad() it is, then. I'll make it do as little as possible. Thanks, all, for your time and advice. On Monday, February 20, 2017 at 7:47:44 AM UTC-7, Stephen Connolly wrote: > > > > On 20 February 2017 at 14:11, Robert St. John

Build details of pipeline job via API

Hi, I'm trying to get information about running builds on Jenkins agents, with and without pipelines. 'Old-style' jobs show up just fine but pipelines only ever appear as placeholder tasks: { "currentExecutable": { "_class":

Using milestone within a parallel task

Hi, There's a restriction currently that prevents the use of a milestone step within a parallel execution of multiple tasks and I'm trying to understand if this is something that we could remove (I would submit a PR), but I'd like to discuss it first. I have multiple jobs with the

Re: plugin data migration - potential incompatibility

On 20 February 2017 at 14:11, Robert St. John wrote: > The only problem I see with the readResolve() solution is the possible > conversion of one build step to many. Unless returning a list of > SimpleBuildStep objects from readResolve() would magically work, > Are you

Re: plugin data migration - potential incompatibility

The only problem I see with the readResolve() solution is the possible conversion of one build step to many. Unless returning a list of SimpleBuildStep objects from readResolve() would magically work, that approach could potentially banish some persisted configuration to the Phantom Zone.

Re: Changelog is now YAML and lives in the site repository

Ok. If main contributors are happy with it, I have nothing to say. Le lun. 20 févr. 2017 à 12:42, Daniel Beck a écrit : > > > On 20.02.2017, at 11:37, Arnaud Héritier wrote: > > > > I don't like to have the changelog leaving outside of the project >

Re: Jelly/Plugin pipeline script support for optionalBlock

> On 20.02.2017, at 12:31, Robert Sandell wrote: > > https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions … which should be only used when there's really no way to make work.

Re: Changelog is now YAML and lives in the site repository

> On 20.02.2017, at 11:37, Arnaud Héritier wrote: > > I don't like to have the changelog leaving outside of the project repository. It already was in the case of LTS (which AFAIK is the line more successful with users since we made it more discoverable on the site), and

Re: Jelly/Plugin pipeline script support for optionalBlock

https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions /B On Sat, Feb 18, 2017 at 5:53 AM, wrote: > > I've finally got it

Re: Changelog is now YAML and lives in the site repository

Even if I understand the technical need, I don't like to have the changelog leaving outside of the project repository. Am I the only one? Aren't we taking a risk to have it outdated? Wasn't it possible to copy it from the project repo to the website build ? On Mon, Feb 20, 2017 at 10:41 AM,

Jenkins developers who are also IntelliJ users, please all pile on this bug

https://youtrack.jetbrains.com/issue/IDEA-168464 Because you have got to be having this issue too! -- 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

Changelog is now YAML and lives in the site repository

Hi everyone, I moved the changelog to the site: https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml All that's left in jenkinsci/jenkins is a tombstone file directing people to the file above: