date:20150324

Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:

On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com
javascript: wrote:
I added a new test to the git client plugin which depended on a Java 7
NIO
feature. It failed to compile in my test configuration with Java 6.

I think it is fine to require Java 7 in tests; there was already a
proposal which met with no controversy to require 7 for building
plugins, while continuing to use -target 6 and Animal Sniffer to
prevent accidental use of 7+ APIs or bytecode (*). Requiring 8 for
building plugins, and thus allowing -source 8 features in
src/test/java/**/*.java (**), would be a natural next step, a bit
controversial but much less so than requiring 8 for running Jenkins
itself.

(*) Of course this means functional tests do not find runtime problems
occurring on 6 despite lack of linkage errors. But the alternative of
running tests on 6 just means the reverse problem, that behavioral
changes in 7 which break the plugin are not caught; and this is worse,
since many more people will really be running on 7.

(**) The upcoming version of Animal Sniffer allows you to skip checks
on test-scope dependencies. But it might not yet allow checks to be
skipped on src/test/java/**/*.java, which is not a dependency; will
need to look into it.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updateing apache tar streams


 You mean you are unsure about the regressions of updating ant to 1.9.4, or do 
 you see other possible regressions?

Yes, both in the changed Tar…Streams and the rest of Ant as used by Jenkins. 
Updating Ant seemed like the way to go and IIRC there's also a bunch of other 
classes added since we copied the classes over that are needed by the Streams. 
However I haven't investigated any further.

I haven't looked further for possible problems, or performed extensive tests 
with the patched build. So this could work without any problems.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/B2FA3874-49D9-49FA-8468-86B5BDA236E5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

I think multi-catch and try with resources are big enough on their own to
take advantage of in java 7 :-)
The syntactic sugar of numerical literals with underscores, and the generic
type inference although sugar will make code more readable.

As for Java8 bringing usefull things, streams to those that aren't in the
know can create very under-performing code when used ([in]correctly) at
scale and Lambdas despite Jesse's love of them are a half baked
implementation that is oft (ab)used to create unintelligible code and the
time API doesn't bring much that we couldn't do if we adopted JodaTime.

+1 to get the next LTS as Java7 only and the one after as Java8 only.

On Tuesday, 24 March 2015 10:42:02 UTC, nicolas de loof wrote:

As said when I opened this topic, I can't see major benefit in requiring
Java 7 from a developer point of view (some syntactic sugar, few new API,
what else ?), compared to huge benefit of Java 8 to review API design and
extensibility.

2015-03-24 11:36 GMT+01:00 Stephen Connolly stephen.al...@gmail.com
javascript::

I think we could start looking at requiring Java 7 as a minimum for
Runtime of Jenkins... given that Maven 3.3.1 has moved its minimum runtime
to Java 7... if we want to bump the evil plugin version to use the Maven
3.3.1 embedded jars we will have to bump Jenkins to require Java 7 as a
minimum... never mind that Java 7 goes EOL next month

On 24 March 2015 at 10:33, James Nord james...@gmail.com javascript:
wrote:

Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:

On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com
wrote:
I added a new test to the git client plugin which depended on a Java
7 NIO
feature. It failed to compile in my test configuration with Java 6.

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com

https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com

https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/030973cc-703d-4314-80b9-a83a1693b3f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multiple post build actions in the same plugin?

2015-03-24 Thread Greg Allen

I have a plugin that implements a post build action by extending 
Notifier. It works fine.


I now want to add another post build action to the same plugin, again 
extending Notifier.


I create the new class that extends Notifier and set up everything the 
same. In fact, I copied the code from the working post build action and 
changed the appropriate names, so I'm pretty sure I've done things 
right. However, my second post build action does not appear in the list 
on the configuration page (but my first still does).  There is nothing 
in any log I can find to indicate a problem.  It just doesn't show up.


Can somebody offer me some suggestions on tracking down what is wrong? I 
feel like I am missing something simple here


Thanks,

-- Greg

--
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55116908.1070603%40redhat.com.
For more options, visit https://groups.google.com/d/optout.

literate multiSCM

2015-03-24 Thread luigi

Dear group,
I think that the literate plugin is really great, and i'd like to modify it 
enabling the use of the MultiSCM plugin, and marking the source that 
contains the marker file to consider for the build process.
I'm totally new in the Jenkins development can someone help me out?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Running Github java files

2015-03-24 Thread simon drake

Good afternoon,

Apologies if this is a very Rookie question but I have searched far and 
wide and haven't been able to find anything of use. I am currently writing 
JUnit Selenium WebDriver tests, using Eclipse, and then 'committing' to a 
private Github repository. 

I cannot seem to find any instructions/documentation on how to create a 
Jenkins job which will run the require .java files from Github? 

If anybody could help I would be most grateful! 

Regards,
Si

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/019dc42f-fe46-4d68-9e08-3619ee21378e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

I have always seen those packages as a convenience and never anything that
was to read into any supportability - especially given that they don't
(didn't) set dependencies correctly and install files to completely
inappropriate locations. (there is a linux FHS for a reason).

So given that, my answer would be I don't care if CentOS 5 doesn't have a
JDK8 in its distribution packages as there is an RPM from Oracle if people
insist on doing it this way (which actually leads to a buggy Jenkins
install which miss-behaves in ways users don't expect!). On top of that
the OpenJDK version 6 which ships with some OS'es that may currently be
used is buggy as hell, so anyone that uses that is just asking for trouble
at present.

/James

On Tuesday, 24 March 2015 10:58:07 UTC, Daniel Beck wrote:

How's availability of Java 8 (and preferably JDK 8 for the tools) on the
default package repos of the various platforms we have native packages for?

On 24.03.2015, at 11:52, Stephen Connolly stephen.al...@gmail.com
javascript: wrote:

Well jumping from Java 6 to Java 8 is a big jump. My point is that we
probably can strongly argue to jump to Java 7 today... then in a few months
(say 3 months after Java 7 is EOL... to allow for an LTS that supports Java
7 but not Java 6) then we bump up to Java 8

On 24 March 2015 at 10:41, nicolas de loof nicolas...@gmail.com
javascript: wrote:
As said when I opened this topic, I can't see major benefit in requiring
Java 7 from a developer point of view (some syntactic sugar, few new API,
what else ?), compared to huge benefit of Java 8 to review API design and
extensibility

2015-03-24 11:36 GMT+01:00 Stephen Connolly stephen.al...@gmail.com
javascript::
I think we could start looking at requiring Java 7 as a minimum for
Runtime of Jenkins... given that Maven 3.3.1 has moved its minimum runtime
to Java 7... if we want to bump the evil plugin version to use the Maven
3.3.1 embedded jars we will have to bump Jenkins to require Java 7 as a
minimum... never mind that Java 7 goes EOL next month

On 24 March 2015 at 10:33, James Nord james...@gmail.com javascript:
wrote:
Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:
On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com
wrote:
I added a new test to the git client plugin which depended on a Java 7
NIO
feature. It failed to compile in my test configuration with Java 6.

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Re: literate multiSCM

All you need to do is make the MultiSCM plugin implement the new SCM API in
the scm-api plugin... then you will get literate for free!

On 24 March 2015 at 14:04, lu...@draios.com wrote:

Dear group,
I think that the literate plugin is really great, and i'd like to modify
it enabling the use of the MultiSCM plugin, and marking the source that
contains the marker file to consider for the build process.
I'm totally new in the Jenkins development can someone help me out?

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyOUH%3D23xq_P76K7SdnvA2tqJ4%2BK1k0trhjRhweBy4YwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GSoC 2015?

Did jenkins ever took part in GSoC? I think there many-many things that 
students can fix/implement in jenkins core or plugins.
https://www.google-melange.com/gsoc/homepage/google/gsoc2015 

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/39a924db-bcf0-4681-a852-ea66e041f24c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC 2015?

If you're asking about 2015, it seems that train has left the station weeks ago 
(org applications Feb 9-20).

Then there's the problem of mentoring. I assume this will take quite a bit of 
time and effort, and I don't know who could do this.

Maybe something to discuss for 2016?

On 24.03.2015, at 11:06, Kanstantsin Shautsou kanstantsin@gmail.com wrote:

 Did jenkins ever took part in GSoC? I think there many-many things that 
 students can fix/implement in jenkins core or plugins.
 https://www.google-melange.com/gsoc/homepage/google/gsoc2015 
 
 -- 
 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 discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/39a924db-bcf0-4681-a852-ea66e041f24c%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/A693568B-DBCC-4215-830B-DE7EF7D4A122%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Updateing apache tar streams

You mean you are unsure about the regressions of updating ant to 1.9.4, or
do you see other possible regressions?

Am Dienstag, 24. März 2015 12:39:39 UTC+1 schrieb Daniel Beck:

FWIW I have this fixed locally. Just get rid of the copies of the
TarInput/OutputStreams in hudson.org.apache.tools.tar, update Ant in
pom.xml from 1.8.3 to 1.9.4, and change the import in TarArchiver. No need
for a patched implementation anymore AFAICT. I just haven't published this
yet because I have no idea what possible regressions might be.

That said, a test in the acceptance test harness may be suitable. It
wouldn't be the first test of this kind, the one for Compress Artifacts
Plugin creates a workspace of 4GB and zips it.

https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/CompressArtifactsPluginTest.java#L89

On 24.03.2015, at 12:28, Olaf Lenz olaf...@gmail.com javascript:
wrote:

Hi!

My name is Olaf Lenz, I'm a software engineer from Germany. Although I
have already made some (small) contributions to various plugins, I have not
yet any experience with Jenkins core development.
What I want to do is to fix the following issue:
https://issues.jenkins-ci.org/browse/JENKINS-10629

At first, I would try to update the Tar{Input,Output}Stream to a recent
version, as suggested by Daniel Beck. If that doesn't solve the issue (from
looking at the code changes I don't think it does), I will see what needs
to be done.

The Contributing to Jenkins-page tells me that I should provide a unit
test for the modification. However, as this is about files 8GB, and
sending these via stream is pretty costly, I am not sure whether it is a
good idea to make this unit test part of the standard test suite. Are there
any suggestions from the experienced developers?

Olaf

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/84dab44f-e3ed-4c66-a9b1-0cd68a4c2db9%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/dcd79c35-3ae6-4bec-b4dc-15e6407518e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

2015-03-24 11:36 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com
:

On 24 March 2015 at 10:33, James Nord jamestn...@gmail.com wrote:

Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:

On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com
wrote:
I added a new test to the git client plugin which depended on a Java 7
NIO
feature. It failed to compile in my test configuration with Java 6.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznmy08LYOn0VPMg%2Bkef84LCP72NhJakbKKKeqfiXD3DSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

How's availability of Java 8 (and preferably JDK 8 for the tools) on the
default package repos of the various platforms we have native packages for?

On 24.03.2015, at 11:52, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:

On 24 March 2015 at 10:41, nicolas de loof nicolas.del...@gmail.com wrote:
As said when I opened this topic, I can't see major benefit in requiring Java
7 from a developer point of view (some syntactic sugar, few new API, what
else ?), compared to huge benefit of Java 8 to review API design and
extensibility

2015-03-24 11:36 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com:
I think we could start looking at requiring Java 7 as a minimum for Runtime
of Jenkins... given that Maven 3.3.1 has moved its minimum runtime to Java
7... if we want to bump the evil plugin version to use the Maven 3.3.1
embedded jars we will have to bump Jenkins to require Java 7 as a minimum...
never mind that Java 7 goes EOL next month

On 24 March 2015 at 10:33, James Nord jamestn...@gmail.com wrote:
Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:
On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com wrote:
I added a new test to the git client plugin which depended on a Java 7 NIO
feature. It failed to compile in my test configuration with Java 6.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznmy08LYOn0VPMg%2Bkef84LCP72NhJakbKKKeqfiXD3DSw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwg-0TN7vSNf3o26X3%2BQTM4S2e90siEqQJPku78JUBokw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Updateing apache tar streams

Hi!

My name is Olaf Lenz, I'm a software engineer from Germany. Although I have 
already made some (small) contributions to various plugins, I have not yet 
any experience with Jenkins core development.
What I want to do is to fix the following issue: 
https://issues.jenkins-ci.org/browse/JENKINS-10629 

At first, I would try to update the Tar{Input,Output}Stream to a recent 
version, as suggested by Daniel Beck. If that doesn't solve the issue (from 
looking at the code changes I don't think it does), I will see what needs 
to be done.

The Contributing to Jenkins-page tells me that I should provide a unit 
test for the modification. However, as this is about files 8GB, and 
sending these via stream is pretty costly, I am not sure whether it is a 
good idea to make this unit test part of the standard test suite. Are there 
any suggestions from the experienced developers?

Olaf

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/84dab44f-e3ed-4c66-a9b1-0cd68a4c2db9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

Java 7 has better file API and jenkins should have better performance. Also
this should allow cleanup stab that do conditioning 6 vs 7 for some parts
of code. Some libraries already start requiring java 1.7. If 1.6 is EOL
then i'm +1 for switching to 1.7 as base line.

On Tuesday, March 24, 2015 at 1:42:02 PM UTC+3, nicolas de loof wrote:

2015-03-24 11:36 GMT+01:00 Stephen Connolly stephen.al...@gmail.com
javascript::

On 24 March 2015 at 10:33, James Nord james...@gmail.com javascript:
wrote:

Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com

https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com

https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/6506e7e4-e1ac-47e0-9bc3-3b53233363c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

I think we could start looking at requiring Java 7 as a minimum for Runtime
of Jenkins... given that Maven 3.3.1 has moved its minimum runtime to Java
7... if we want to bump the evil plugin version to use the Maven 3.3.1
embedded jars we will have to bump Jenkins to require Java 7 as a
minimum... never mind that Java 7 goes EOL next month

On 24 March 2015 at 10:33, James Nord jamestn...@gmail.com wrote:

Rejoice! IBM AIX and z/OS now have a GA Java8 version.

http://www-01.ibm.com/support/docview.wss?uid=swg21696670

Is it time to revisit this once more?

/James

On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:

On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite mark.ea...@gmail.com
wrote:
I added a new test to the git client plugin which depended on a Java 7
NIO
feature. It failed to compile in my test configuration with Java 6.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Updateing apache tar streams

FWIW I have this fixed locally. Just get rid of the copies of the
TarInput/OutputStreams in hudson.org.apache.tools.tar, update Ant in pom.xml
from 1.8.3 to 1.9.4, and change the import in TarArchiver. No need for a
patched implementation anymore AFAICT. I just haven't published this yet
because I have no idea what possible regressions might be.

That said, a test in the acceptance test harness may be suitable. It wouldn't
be the first test of this kind, the one for Compress Artifacts Plugin creates a
workspace of 4GB and zips it.

https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/test/java/plugins/CompressArtifactsPluginTest.java#L89

On 24.03.2015, at 12:28, Olaf Lenz olaf.l...@gmail.com wrote:

Hi!

My name is Olaf Lenz, I'm a software engineer from Germany. Although I have
already made some (small) contributions to various plugins, I have not yet
any experience with Jenkins core development.
What I want to do is to fix the following issue:
https://issues.jenkins-ci.org/browse/JENKINS-10629

The Contributing to Jenkins-page tells me that I should provide a unit test
for the modification. However, as this is about files 8GB, and sending these
via stream is pretty costly, I am not sure whether it is a good idea to make
this unit test part of the standard test suite. Are there any suggestions
from the experienced developers?

Olaf

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/84dab44f-e3ed-4c66-a9b1-0cd68a4c2db9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/88E55117-93BC-4689-B318-BC771EBC88C0%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC 2015?

Yes, i'm late :(

On Tuesday, March 24, 2015 at 1:51:32 PM UTC+3, Daniel Beck wrote:

If you're asking about 2015, it seems that train has left the station
weeks ago (org applications Feb 9-20).

Then there's the problem of mentoring. I assume this will take quite a bit
of time and effort, and I don't know who could do this.

Maybe something to discuss for 2016?

On 24.03.2015, at 11:06, Kanstantsin Shautsou kanstan...@gmail.com
javascript: wrote:

Did jenkins ever took part in GSoC? I think there many-many things that
students can fix/implement in jenkins core or plugins.
https://www.google-melange.com/gsoc/homepage/google/gsoc2015

--
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-de...@googlegroups.com javascript:.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/39a924db-bcf0-4681-a852-ea66e041f24c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/6bfb975e-b462-44cd-851f-dda29edf3a52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

SpringFramework did switch to 2.0 as they dropped support for java 1.3 - no
internal refactoring, just a major version upgrade to warn people about
some significant change they need to consider with care.

2015-03-24 22:03 GMT+01:00 Christopher Orr ch...@orr.me.uk:

 I don't actually know how the startup / WAR extraction stuff works, but I
 did wonder whether a Java 6-compatible piece of code could be run at
 startup to print a Jenkins now requires Java 8 warning to the console.

 But in any case, we need to warn users well in advance of upgrading.  A
 lot of people won't be happy if they hit the upgrade button in the UI only
 to find that Jenkins doesn't come up again.



 On 24/03/15 13:51, Kanstantsin Shautsou wrote:

 I think jenkins can check java version on startup and print friendly
 message to log instead of some java related stacktraces.

  On Mar 24, 2015, at 23:46, Christopher Orr ch...@orr.me.uk wrote:

 Yeah, since we're upgrading, it may as well be to Java 8 since it (seems
 to be) be available for every OS we package for, and it would minimise the
 pain for users, rather than splitting it across two updates.

 I don't think we specify the required Java version in most of our native
 package specs, and WAR users upgrading will have no way of knowing about
 the Java requirement change, so we probably need to do a lot of user
 education in advance.

 Maybe we can have banners inside the web interface for one or two
 releases in advance, warning about the impending Java version requirement?
 Plus big red text in the changelog, articles on the blog, Twitter etc.

 Some banners on the website, wiki and issue tracker (as we sometimes do,
 e.g. for donation or JUC advertising) would also be a good idea.

 Regards,
 Chris


 On 24/09/14 12:40, Baptiste Mathus wrote:

 I'm absolutely +1 on the advantages on the programming model that
 defining a JDK8 as a minimum JDK would give us. And like Nicolas, I also
 think JDK7 is not really worth it as 8 is.

 And Jenkins is one of those tools that has somehow a lower barrier on
 that requirement upgrade, since for example the build JDK can a totally
 different one, or wouldn't impact say a ruby/C/whatever compiler anyway.

 Btw, I guess we own at least of those AIX installs, and JDK are actually
 generally not so that behind. JDK8 for AIX seems to be not GA *yet* but
 I'm sure IBM is working on it if not already out (found
 http://www.ibm.com/developerworks/java/jdk/beta/ for example).
 Sure, old platform like AIX 4 or 5.x wouldn't have those JDK supported,
 so I suppose there could be some Jenkins VeryLTS to keep Java 6 as it's
 now for say some months or even a year for only very important issues.
 That would give time for those platform a bit more time to provide the
 JDK8 port/version for their OS.

 2014-09-24 19:42 GMT+02:00 Daniel Beck m...@beckweb.net
 mailto:m...@beckweb.net:


 On 24.09.2014, at 11:48, Martin Kutter martin.kut...@fen-net.de
 mailto:martin.kut...@fen-net.de wrote:

  Just want to throw in that java 8 is not yet available on all
 platforms
  (like AIX, HP-UX and probably some other less frequently used
 commercial
  UNIXes).

 I checked the anonymous usage stats a few weeks ago:
 Out of 93,400 installs, we know the master's OS for 85,200 of them.
 285 are AIX. 120 are HP-UX. 50 installs total on OpenBSD, Darwin,
 OS/400, z/OS and NetBSD.

 Not relevant enough IMO if the advantages are significant.

 I can provide the queries I used if anyone wants to verify these.

 --
 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
 mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor ! nbsp;!

 --
 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
 mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Developers group.
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/jenkinsci-dev/5511CD16.6090302%40orr.me.uk.
 For more options, visit https://groups.google.com/d/optout.



 --
 You received this message because you are subscribed to the Google Groups

Re: Proposal : Jenkins to require Java 8

2015-03-24 22:38 GMT+01:00 Suckow, Thomas J thomas.suc...@pnnl.gov:

What prevent you to get JDK8 on slave to run the remoting agent, but use
JDK installer to build your legacy JDK 1.1 application ?

In many cases this is possible. I don't think this is documented all that
well though (I've done it once and it took me a while to get it right). I
would imagine this is something that should be in an upgrade guide. If you
can't run JDK8, then you get to run a legacy Jenkins install.

Didn't you just configured a JDK installation and select it from your job
configuration ?

Sorry, but rhel5 is not something that we should care about, AFAIR it on
extended support. You can still use ancient jenkins version and ask RHEL
support to do patches for jenkins. RHEL6 and RHEL7 were released long
time ago - update your infra.

I don't think we should be making sure NEW release cycles support RHEL5.
It is in extended support, people in that environment should be
comfortable dealing with tools from that era. That said, there are ways to
make it work, but it shouldn't be blessed.

And it's simply not possible to update Jenkins (master) in isolation,
the remoting model requires that all slaves use similar JREs, and satisfy
the minimum requirements.

But we shouldn't stay at Java6 forever. I am seeing a lot of hints at
making some radical changes/improvements. Should we really be talking of a
Jenkins2 and not expect people to auto-update to it? We could offer 1 or 2
more LTS on the 1.x track.

What would change in 3/ 6 months ?
Lot's of people will still run RHEL 5 and build legacy Java 1.3
applications.

-
Thomas

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/D1372128.11495%25thomas.suckow%40pnnl.gov
.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzkzTA_R7-htBD_4nUD3CqfuSEreoSuf-g1rpu7XkaQJRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

Proposal is not to maintain parallel branches, but to make next release to
require Java 8 and start using it for new development / step by step
enhance existing APIs to benefit Java 8

What would change in 3/ 6 months ?
Lot's of people will still run RHEL 5 and build legacy Java 1.3
applications.

Ok, maybe 10 LTS's then. We need to have a plan for supporting the past
and the future. If we do have so many people wanting the java6 branch,
then they should be able to support it. It sounds like we have a large
number of people interested in java8 and I don't think such a transition
will be ready for quite some time. I imagine we will also have people using
both and maintaining both. I still have RHEL5 and a SPARC and I will do
what I have to with those as long as I need to. But I also have bleeding
edge items and I'd like to see Jenkins continue to push that envelope. This
is a community, I can't imagine that if the mainline moved on to Java8 we
wouldn't still help those who are still using the current mainline.

-
Thomas

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/D13733B8.11501%25thomas.suckow%40pnnl.gov
https://groups.google.com/d/msgid/jenkinsci-dev/D13733B8.11501%25thomas.suckow%40pnnl.gov?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznBdm3DmnZ_GO0viCawUek0yXj3jnSiZR%3DoDpHObR%2BSvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

2015-03-24 Thread Suckow, Thomas J

Didn't you just configured a JDK installation and select it from your job
configuration ?
Ya. Once I know how that works. I didn't expect it to be a global jenkins
configuration when I only have that setup on a single slave. Maybe I am a bit
slow. I also configured the slave to start with the desired jdk and was
surprised when the job didn't use that same slave.

What would change in 3/ 6 months ?
Lot's of people will still run RHEL 5 and build legacy Java 1.3 applications.

Ok, maybe 10 LTS's then. We need to have a plan for supporting the past and the
future. If we do have so many people wanting the java6 branch, then they
should be able to support it. It sounds like we have a large number of people
interested in java8 and I don't think such a transition will be ready for quite
some time. I imagine we will also have people using both and maintaining both.
I still have RHEL5 and a SPARC and I will do what I have to with those as long
as I need to. But I also have bleeding edge items and I'd like to see Jenkins
continue to push that envelope. This is a community, I can't imagine that if
the mainline moved on to Java8 we wouldn't still help those who are still using
the current mainline.

-
Thomas

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/D13733B8.11501%25thomas.suckow%40pnnl.gov.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

2015-03-24 Thread Suckow, Thomas J

What prevent you to get JDK8 on slave to run the remoting agent, but use
JDK installer to build your legacy JDK 1.1 application ?

And it's simply not possible to update Jenkins (master) in isolation,
the remoting model requires that all slaves use similar JREs, and satisfy
the minimum requirements.

-
Thomas

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/D1372128.11495%25thomas.suckow%40pnnl.gov.
For more options, visit https://groups.google.com/d/optout.

Re: Problems building jenkins


On 24.03.2015, at 15:32, Olaf Lenz olaf.l...@gmail.com wrote:

 Are there any objections?

Recommendations like that probably shouldn't be front and center where new 
contributors pick them up as the recommended settings. We want the tests to 
pass, after all.

If there's a simple way to determine whether the group policy allows symbolic 
links and maybe skip the tests if disallowed, that would be a feasible solution 
to this issue IMO.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/120FDFE4-5547-4518-A7DD-4C2A9D4DD5F1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: literate multiSCM

2015-03-24 Thread Luigi Tagliamonte

Thank you Stephen,
can you point me to the interface to implement?

On Tue, Mar 24, 2015 at 3:17 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:

All you need to do is make the MultiSCM plugin implement the new SCM API
in the scm-api plugin... then you will get literate for free!

On 24 March 2015 at 14:04, lu...@draios.com wrote:

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the
Google Groups Jenkins Developers group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/HFyKH8C-EHE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyOUH%3D23xq_P76K7SdnvA2tqJ4%2BK1k0trhjRhweBy4YwA%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyOUH%3D23xq_P76K7SdnvA2tqJ4%2BK1k0trhjRhweBy4YwA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
Luigi
---
“The only way to get smarter is by playing a smarter opponent.”

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CADbyipCOr8VMOFzYUU_kqFkp9ig%2BnZ_AEWnEMbfMJrWk%2BS2KtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: literate multiSCM

I'm sure he has *some* idea... it will be interesting to see how that
problem gets unpicked...

On 24 March 2015 at 15:50, Jesse Glick jgl...@cloudbees.com wrote:

On Tue, Mar 24, 2015 at 10:17 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
All you need to do is make the MultiSCM plugin implement the new SCM API
in
the scm-api plugin... then you will get literate for free!

Although how exactly it should implement it is unclear to me.
multiple-scms produces checkouts from several repos. Which one would
you search for branches? What would such an integration be good 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 this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Yqvt-JhW6r_M6-BjfX0Mot-c8PCcnOWAHM0pznFyzOA%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxLSBRKczLhi%2BvRXRctG_cB7UTAD%2BhzD6TrHQJ%2BJQ6TuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: literate multiSCM

2015-03-24 Thread Jesse Glick

On Tue, Mar 24, 2015 at 10:17 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
 All you need to do is make the MultiSCM plugin implement the new SCM API in
 the scm-api plugin... then you will get literate for free!

Although how exactly it should implement it is unclear to me.
multiple-scms produces checkouts from several repos. Which one would
you search for branches? What would such an integration be good 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 this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Yqvt-JhW6r_M6-BjfX0Mot-c8PCcnOWAHM0pznFyzOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems building jenkins

There's a few issues in building on windows - the test harness can hide
useful failure traces in plugins etc..
and they are slowly starting to be ironed out - we may also have a windows
build machine soon so we can do the build/testing on windows...

Jenkins already detects that symbolic links aren't enabled on a windows box
when running - so it shouldn't be to hard to actually put in an assumeThat
and check the platform. (unless it does this by trying to create a symlink
to begin with...)
IIRC a group policy is just a fancy way of controlling a load of registry
settings - in which case JNA can be used to read the key.

/James

On Tuesday, 24 March 2015 14:39:11 UTC, Daniel Beck wrote:

On 24.03.2015, at 15:32, Olaf Lenz olaf...@gmail.com javascript:
wrote:

Are there any objections?

Recommendations like that probably shouldn't be front and center where new
contributors pick them up as the recommended settings. We want the tests
to pass, after all.

If there's a simple way to determine whether the group policy allows
symbolic links and maybe skip the tests if disallowed, that would be a
feasible solution to this issue IMO.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/38356f54-6071-4ada-8b90-704a80edf180%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems building jenkins

I forgot to attach the output of the mvn build, here it is. It doesn't look 
as though it is only the symbolic link problem.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/656e86ea-f3c1-4b20-94a8-391d9b132df4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[DEBUG]   (s) projectArtifactMap = 
{org.jenkins-ci.plugins.icon-shim:icon-set=org.jenkins-ci.plugins.icon-shim:icon-set:jar:1.0.5:compile,
 org.jenkins-ci.main:remoting=org.jenkins-ci.main:remoting:jar:2.50:compile, 
org.jenkins-ci:constant-pool-scanner=org.jenkins-ci:constant-pool-scanner:jar:1.2:compile,
 org.jenkins-ci.main:cli=org.jenkins-ci.main:cli:jar:1.607-SNAPSHOT:compile, 
org.jenkins-ci:version-number=org.jenkins-ci:version-number:jar:1.1:compile, 
org.jenkins-ci:crypto-util=org.jenkins-ci:crypto-util:jar:1.1:compile, 
org.jvnet.hudson:jtidy=org.jvnet.hudson:jtidy:jar:4aug2000r7-dev-hudson-1:compile,
 
org.jenkins-ci:core-annotation-processors=org.jenkins-ci:core-annotation-processors:jar:1.0:provided,
 com.google.inject:guice=com.google.inject:guice:jar:4.0-beta:compile, 
javax.inject:javax.inject=javax.inject:javax.inject:jar:1:compile, 
aopalliance:aopalliance=aopalliance:aopalliance:jar:1.0:compile, 
org.jruby.ext.posix:jna-posix=org.jruby.ext.posix:jna-posix:jar:1.0.3-jenkins-1:compile,
 com.github.jnr:jnr-posix=com.github.jnr:jnr-posix:jar:3.0.1:compile, 
com.github.jnr:jnr-ffi=com.github.jnr:jnr-ffi:jar:1.0.7:compile, 
com.github.jnr:jffi=com.github.jnr:jffi:jar:native:1.2.7:runtime, 
org.ow2.asm:asm=org.ow2.asm:asm:jar:4.0:compile, 
org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:4.0:compile, 
org.ow2.asm:asm-analysis=org.ow2.asm:asm-analysis:jar:4.0:compile, 
org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:4.0:compile, 
org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:4.0:compile, 
com.github.jnr:jnr-x86asm=com.github.jnr:jnr-x86asm:jar:1.0.2:compile, 
com.github.jnr:jnr-constants=com.github.jnr:jnr-constants:jar:0.8.5:compile, 
org.kohsuke:trilead-putty-extension=org.kohsuke:trilead-putty-extension:jar:1.2:compile,
 
org.jenkins-ci:trilead-ssh2=org.jenkins-ci:trilead-ssh2:jar:build217-jenkins-8:compile,
 
org.kohsuke.stapler:stapler-groovy=org.kohsuke.stapler:stapler-groovy:jar:1.236:compile,
 
org.kohsuke.stapler:stapler-jelly=org.kohsuke.stapler:stapler-jelly:jar:1.236:compile,
 
org.jenkins-ci:commons-jelly=org.jenkins-ci:commons-jelly:jar:1.1-jenkins-20120928:compile,
 
org.jenkins-ci.dom4j:dom4j=org.jenkins-ci.dom4j:dom4j:jar:1.6.1-jenkins-4:compile,
 
org.kohsuke.stapler:stapler-jrebel=org.kohsuke.stapler:stapler-jrebel:jar:1.236:compile,
 org.kohsuke.stapler:stapler=org.kohsuke.stapler:stapler:jar:1.236:compile, 
javax.annotation:javax.annotation-api=javax.annotation:javax.annotation-api:jar:1.2:compile,
 
commons-discovery:commons-discovery=commons-discovery:commons-discovery:jar:0.4:compile,
 org.jvnet:tiger-types=org.jvnet:tiger-types:jar:1.3:compile, 
org.kohsuke:windows-package-checker=org.kohsuke:windows-package-checker:jar:1.0:compile,
 
org.kohsuke.stapler:stapler-adjunct-zeroclipboard=org.kohsuke.stapler:stapler-adjunct-zeroclipboard:jar:1.3.5-1:compile,
 
org.kohsuke.stapler:stapler-adjunct-timeline=org.kohsuke.stapler:stapler-adjunct-timeline:jar:tests:1.4:test,
 
org.kohsuke.stapler:stapler-adjunct-codemirror=org.kohsuke.stapler:stapler-adjunct-codemirror:jar:1.3:compile,
 
com.infradna.tool:bridge-method-annotation=com.infradna.tool:bridge-method-annotation:jar:1.13:compile,
 
org.kohsuke.stapler:json-lib=org.kohsuke.stapler:json-lib:jar:2.4-jenkins-2:compile,
 net.sf.ezmorph:ezmorph=net.sf.ezmorph:ezmorph:jar:1.0.6:compile, 
commons-httpclient:commons-httpclient=commons-httpclient:commons-httpclient:jar:3.1:compile,
 args4j:args4j=args4j:args4j:jar:2.0.31:compile, 
org.jenkins-ci:annotation-indexer=org.jenkins-ci:annotation-indexer:jar:1.7:compile,
 
org.jenkins-ci:bytecode-compatibility-transformer=org.jenkins-ci:bytecode-compatibility-transformer:jar:1.5:compile,
 org.kohsuke:asm5=org.kohsuke:asm5:jar:5.0.1:compile, 
org.jenkins-ci:task-reactor=org.jenkins-ci:task-reactor:jar:1.4:compile, 
org.jvnet.localizer:localizer=org.jvnet.localizer:localizer:jar:1.23:compile, 
antlr:antlr=antlr:antlr:jar:2.7.6:compile, 
org.jvnet.hudson:xstream=org.jvnet.hudson:xstream:jar:1.4.7-jenkins-1:compile, 
jfree:jfreechart=jfree:jfreechart:jar:1.0.9:compile, 
jfree:jcommon=jfree:jcommon:jar:1.0.12:compile, 
org.apache.ant:ant=org.apache.ant:ant:jar:1.8.4:compile, 
org.apache.ant:ant-launcher=org.apache.ant:ant-launcher:jar:1.8.4:compile, 
javax.servlet:servlet-api=javax.servlet:servlet-api:jar:2.4:provided, 
commons-io:commons-io=commons-io:commons-io:jar:2.4:compile,

Problems building jenkins

Hi!

I am a Jenkins core devel newbie.
Meanwhile, I have managed to get the Jenkins master branch to build, based
on the BUILDING.txt file in the sources. However, I first tried to build
using https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins , which
didn't work. I would like to fix the Wiki page, but I need some help for
that.

Here is what I tried, and how it failed. Note that I am working on Windows
7.

I cloned the git repo and ran mvn -Plight-test install. When doing so,
the build fails in the core component in some of the unit tests that were
executed. I have attached the output of the mvn call to this message. A
part of the problem seems to be that on Windows, symbolic links are not
allowed by default, but that is not all.

So I thought that if the problem is just that some unit test fails, I
simply disable the unit tests for now. On the wiki page, it is stated that
to skip the tests, one can use -Dskip-test-harness. Unfortunately, that
didn't have any effect, the build still fails. If I understand it right,
skip-test-harness will skip the independent test harness, which runs the
integration tests, but the unit tests still run, right?

From BUILIDNG.txt, I saw the option -DskipTests. When using that, jenkins
finally builds.

So, my proposal or the wiki page would be:

- To add the command from BUILDING.txt for the very first trial to
build jenkins.
- To hint at the option -DskipTests if the first normal build (with
mvn install) fails

Are there any objections? Or is there anything wrong in what I did?

Olaf

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/be497805-fbf5-402c-828b-686a9b1a4fff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: literate multiSCM

https://github.com/jenkinsci/scm-api-plugin/blob/master/src/main/java/jenkins/scm/api/SCMSource.java

On 24 March 2015 at 14:41, Luigi Tagliamonte lu...@draios.com wrote:

Thank you Stephen,
can you point me to the interface to implement?

On Tue, Mar 24, 2015 at 3:17 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:

All you need to do is make the MultiSCM plugin implement the new SCM API
in the scm-api plugin... then you will get literate for free!

On 24 March 2015 at 14:04, lu...@draios.com wrote:

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/5d41deed-b1b5-4488-82e1-04f8c73f428b%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

For more options, visit https://groups.google.com/d/optout.

--
Luigi
---
“The only way to get smarter is by playing a smarter opponent.”

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CADbyipCOr8VMOFzYUU_kqFkp9ig%2BnZ_AEWnEMbfMJrWk%2BS2KtQ%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CADbyipCOr8VMOFzYUU_kqFkp9ig%2BnZ_AEWnEMbfMJrWk%2BS2KtQ%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxCv%2BOAQ5HRcR0hNqdsEiNB-UjSA70%2B0u_tF8XGNY82UA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins icons for Disabled and Aborted job status plugin

2015-03-24 Thread Rocky Stone

One (hopefully) last bump.

On Tue, Jan 27, 2015 at 6:52 PM, Rocky Stone rstone.m...@gmail.com wrote:

Sorry for the delay. I deleted the repo and created new one that isn't
branched from the jenkins repo on the same URL:
https://github.com/kralq/distinguishable-gray-balls-plugin

On Mon, Jan 26, 2015 at 8:12 PM, Daniel Beck m...@beckweb.net wrote:

Thanks for the reminder!

I don't know what'll happen when I try to fork this after you've forked
it from jenkinsci (despite it being unrelated in functionality). Since the
UI doesn't allow it to be forked, I fear for the original repo...

Could you delete your repo (keeping your source code of course) and
create a new one from scratch so it's no longer related to
jenkinsci/greenballs-plugin? You don't have history anyway, so starting
with the current code state as 'initial commit' wouldn't be a big issue I
think.

On 26.01.2015, at 16:31, Rocky Stone rstone.m...@gmail.com wrote:

Bump!

Could anyone please review the suggested plug-in (and eventually
approve commit access for jenkins repository)?

On Wed, Dec 17, 2014 at 1:24 PM, Rocky Stone rstone.m...@gmail.com
wrote:
Thanks Daniel for replying to Slide, you have explained it better that
I would have :)

And thanks the valuable feedback, it is very welcome!

I renamed the plugin to Distinguishable Gray Balls, renamed the package
name and updated the logger.

On Tue, Dec 16, 2014 at 8:46 PM, Daniel Beck m...@beckweb.net wrote:
I had the same initial reaction. However, note that this plugin retains
the blue balls. It just does something similar with to the grey balls only
(i.e. likely a similar implementation, which isn't a great indicator WRT
which plugins should be combined). While Green Balls deals with the
blue/green (and in per-user color-blind mode yellow and red) balls, this
one processes the grey balls only. 'Fork' in this case just means I copied
a bunch of code.

And if these were merged, you'd need several new global options:

* Blue or green (in the former case, no color blindness options should
be offered to users)
* Differentiate between aborted, disabled and not built Y/N

The well-established name 'Green Balls' would also become somewhat
misleading as it wouldn't cover half the feature set.

It'd just be a mess.

---

That said, 'job-status-icons-plugin' seems a bit too generic. It
doesn't tell you anything about what it does. Since the author appears to
not want to extend the feature set a lot beyond what it already does,
'distinguishable-grey-icons' or something might be better.

And while I'm nitpicking, this line should also be changed:

https://github.com/kralq/job-status-icons-plugin/blob/master/src/main/java/hudson/plugins/statusicons/StatusIconFilter.java#L30

On 16.12.2014, at 19:29, Slide slide.o@gmail.com wrote:

Why do you prefer not to merge it with Green Balls? If the plugins
basically have the same root, I think it would be better to merge into an
existing plugin rather than creating a new one.

On Tue Dec 16 2014 at 11:09:00 AM Rocky Stone rstone.m...@gmail.com
wrote:
Hi Jenkins Devs,

I would like to add a plugin forked from Green Balls that adds icons
for Disabled and Aborted job status.

GitHub plugin name: job-status-icons-plugin
Personal GitHub ID: kralq
Existing GitHub repository:
https://github.com/kralq/job-status-icons-plugin

IMHO it's best to update the default Jenkins icons, and I'll be happy
if the Jenkins developers consider using the very simple icons I created
based on the gray ball icon.

The plugin will still be useful for people that aren't using the
latest and greatest (e.g. on the LTS release channel), so I would like to
publish it even if the default Jenkins icons get updated.

I read in the wiki that it's best to contribute to existing plugins
rather than creating new ones, but this contradicts to the KISS principle.
So even though I basically copied the Green Balls plugin and updated the
svg icons I prefer not to merge it with Green Balls. Moreover the plugin is
compatible with both blue and green success status icon.

Thanks,
Rocky

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAHZdiZGO7B3OTjvy%3DQCdBwBKZCH-xtiTkdpbX2fORJV9-e0%3DKw%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple post build actions in the same plugin?

2015-03-24 Thread Ulli Hafner

Did you provide 2 descriptors?

Am 24.03.2015 um 14:39 schrieb Greg Allen gal...@redhat.com:

I have a plugin that implements a post build action by extending Notifier. It
works fine.

I now want to add another post build action to the same plugin, again
extending Notifier.

I create the new class that extends Notifier and set up everything the same.
In fact, I copied the code from the working post build action and changed the
appropriate names, so I'm pretty sure I've done things right. However, my
second post build action does not appear in the list on the configuration
page (but my first still does). There is nothing in any log I can find to
indicate a problem. It just doesn't show up.

Can somebody offer me some suggestions on tracking down what is wrong? I feel
like I am missing something simple here

Thanks,

-- Greg

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55116908.1070603%40redhat.com.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/78E712C7-4A76-4DE1-9959-57A629725847%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc
Description: Message signed with OpenPGP using GPGMail

FilePath act fails with an exception

2015-03-24 Thread Sverre Moe

Trying the following in Jenkins Script Console:

import hudson.FilePath.FileCallable
import hudson.remoting.VirtualChannel

def jenkinsInstance = jenkins.model.Jenkins.getInstance()
def project = jenkinsInstance.getItem(myMatrixProject)
def rootProject = project.getRootProject()
def someWorkspace = rootProject.getSomeWorkspace()

try { 
def test = someWorkspace.act(new FileCallableString() {
private static final long serialVersionUID = 1;
@Override
public String invoke(File file, VirtualChannel channel) {
return Testing Testing;
}
});
} catch (IOException e) { 
  e.printStackTrace(); 
} catch (InterruptedException e) { 
  e.printStackTrace(); 
}

It throws an exception:

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Script1.groovy: 10: Can't have an abstract method in a non-abstract class. The 
class 'Script1$1' must be declared abstract or the method 'void 
checkRoles(org.jenkinsci.remoting.RoleChecker)' must be implemented.
 @ line 10, column 61.
   ct(new FileCallableString() {

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b2502c2c-8a02-46df-8bce-90ee10724090%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems building jenkins

It turns out that the problems I had were connected to me using Windows...
After I have now switched to Linux for that matter, compilation works fine. 
;-)
It might be worth mentioning on the Wiki page that Jenkins is mainly 
developed on *nix and that there may be some problems with Windows.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8948dd1f-825a-4f25-9806-3be60af3a53f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

2015-03-24 Thread Jesse Glick

On Tue, Mar 24, 2015 at 6:41 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
 I can't see major benefit in requiring Java 7 from a developer point of view 
 (some syntactic sugar, few new API

java.nio.file.* is actually rather important for Jenkins code,
particularly in core, since it uses the filesystem so heavily.

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1%2BwP_j6S7_RtoLH_SYTjdO8Bs-QxEod520hhe5xKv7AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running Github java files


This is a question better suited to the jenkinsci-users mailing list.

-Chris


On 24/03/15 06:57, simon drake wrote:

Good afternoon,

Apologies if this is a very Rookie question but I have searched far and
wide and haven't been able to find anything of use. I am currently
writing JUnit Selenium WebDriver tests, using Eclipse, and then
'committing' to a private Github repository.

I cannot seem to find any instructions/documentation on how to create a
Jenkins job which will run the require .java files from Github?

If anybody could help I would be most grateful!

Regards,
Si


--
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5511B89E.1030602%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Running Github java files

2015-03-24 Thread simon drake

Hi Chris, 

My apologies and thanks. Is this forum more suited for the advanced users of 
Jenkins?

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4e007bac-6e8a-4972-916d-050f84206596%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running Github java files

2015-03-24 Thread Richard Bywater

This particular forum is for development *of* Jenkins or its plugins.

Richard.

On Wed, 25 Mar 2015 at 08:21 simon drake simondrake1...@googlemail.com
wrote:

 Hi Chris,

 My apologies and thanks. Is this forum more suited for the advanced users
 of Jenkins?

 --
 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 discussion on the web visit https://groups.google.com/d/
 msgid/jenkinsci-dev/4e007bac-6e8a-4972-916d-050f84206596%
 40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947SdzEsg-qaEAiXfem4Cs45HE--vEibsUpbX8Fpqoi35Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running Github java files

2015-03-24 Thread simon drake

Ah I see! Thanks guys, I have re-posted! I barely understand Jenkins as it is 
so don't belong here :-)

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/145a33e1-8464-4164-99a4-a912abc58b3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

2015-03-24 Thread Richard Bywater

+1 for Java 7, -1 for Java 8 (at this time). Reason for that is that I
don't believe there is any normal way for RHEL5 servers to get Java 8 and
it will not be hitting its end of production phase until March 2017 and
so I'm guessing there's still a lot out there.

Richard.

On Wed, 25 Mar 2015 at 08:07 Jesse Glick jgl...@cloudbees.com wrote:

On Tue, Mar 24, 2015 at 6:41 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
I can't see major benefit in requiring Java 7 from a developer point of
view (some syntactic sugar, few new API

java.nio.file.* is actually rather important for Jenkins code,
particularly in core, since it uses the filesystem so heavily.

--
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 discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-dev/CANfRfr1%2BwP_j6S7_RtoLH_SYTjdO8Bs-
QxEod520hhe5xKv7AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui9471xSn_NknofC4H%2BaScs_j7oi%2B%2BpJcvEsz59CYgX81jdA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

+1 for Java 7, -1 for Java 8 (at this time). Reason for that is that I don't
believe there is any normal way for RHEL5 servers to get Java 8 and it will
not be hitting its end of production phase until March 2017 and so I'm
guessing there's still a lot out there.

Richard.

On Wed, 25 Mar 2015 at 08:07 Jesse Glick jgl...@cloudbees.com
mailto:jgl...@cloudbees.com wrote:
On Tue, Mar 24, 2015 at 6:41 AM, nicolas de loof
nicolas.del...@gmail.com mailto:nicolas.del...@gmail.com wrote:
I can't see major benefit in requiring Java 7 from a developer point of
view (some syntactic sugar, few new API

java.nio.file.* is actually rather important for Jenkins code,
particularly in core, since it uses the filesystem so heavily.

--
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
mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1%2BwP_j6S7_RtoLH_SYTjdO8Bs-QxEod520hhe5xKv7AQ%40mail.gmail.com

https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1%2BwP_j6S7_RtoLH_SYTjdO8Bs-QxEod520hhe5xKv7AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google
Groups Jenkins Developers group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe
https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui9471xSn_NknofC4H%2BaScs_j7oi%2B%2BpJcvEsz59CYgX81jdA%40mail.gmail.com

https://groups.google.com/d/msgid/jenkinsci-dev/CAMui9471xSn_NknofC4H%2BaScs_j7oi%2B%2BpJcvEsz59CYgX81jdA%40mail.gmail.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2EDF677B-14F1-478C-A2D5-4BC1514AAB06%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Hosting for Stash Pull Request Builder

Even although it appears to be for an internal system, I hope the
credentials in the ApiTest class are old...

-Chris

On 23/03/15 01:33, Nathan McC wrote:

Thanks. Updated the wiki with how to.

Would it be possible to get this into the jenkins ci on github to make
this official.

I'm assuming once I have a repo and permissions to do a relase the rest
of the info on the wiki page will populate.

On Monday, March 23, 2015 at 6:04:23 PM UTC+11, Dominik Bartholdi wrote:

Thats about the info I would expect on the plugins wiki page…
Domi

On 23 Mar 2015, at 01:24, Nathan McC nathan...@gmail.com
javascript: wrote:

Add a blog post with some screenshots;
http://blog.nemccarthy.me/?p=387 http://blog.nemccarthy.me/?p=387

On Sunday, March 22, 2015 at 9:08:59 PM UTC+11, Nathan McC wrote:

Hey guys,

I've made a new Pull Request builder plugin for Stash, this
plugin is inspired by the GitHub and BitBucket PR builder
plugins.

plugin name: stash-pullrequest-builder-plugin
github username: nemccarthy
github repo:
https://github.com/nemccarthy/stash-pullrequest-builder-plugin
https://github.com/nemccarthy/stash-pullrequest-builder-plugin

Wiki page;

https://wiki.jenkins-ci.org/display/JENKINS/Stash+pullrequest+builder+plugin

It would be awesome if I could get this one hosted.

Cheers,
Nathan

https://groups.google.com/d/msgid/jenkinsci-dev/fb3a0eed-4bb7-4c07-a674-ace54f0c0ac7%40googlegroups.com

https://groups.google.com/d/msgid/jenkinsci-dev/fb3a0eed-4bb7-4c07-a674-ace54f0c0ac7%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.

--
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/bc32495a-e3a0-4b7e-9689-ffa8377a6f7a%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/bc32495a-e3a0-4b7e-9689-ffa8377a6f7a%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55110823.7050902%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: AdvancedInstaller Plugin

Regarding the (as-yet undocumented) purpose, I guess the plugin is for
this generically-named piece of software:

http://www.advancedinstaller.com/

Maybe advanced-installer-msi-builder would be a slightly more helpful
and informative plugin ID?

-Chris

On 23/03/15 23:48, Oleg Nenashev wrote:

As I see, the plugin does not exist in your repo.
Could you clarify the purpose of the plugin (e.g. describe the use-case
in details)? There're many plugins, which may address your use-case. As
example, Custom Tools allows to setup an environment for builds.

вторник, 24 марта 2015 г., 9:27:51 UTC+3 пользователь advinst caphyon
написал:

Hello

I would like to request to host a Jenkins CI plugin for building
setups using Advanced Installer

Characteristics of plugin:
- Plugin will add a build step allowing setup builds using Advanced
Installer.

INFORMATION REQUESTED

*GitHub plugin name* : advancedinstaller-plugin

*Personal GitHub ID* : advinst

Thanks!

--
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3df34168-d39d-41d9-b9db-4258d2e697a3%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/3df34168-d39d-41d9-b9db-4258d2e697a3%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55110A65.1050008%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: AdvancedInstaller Plugin

2015-03-24 Thread advinst caphyon

Thanks for the reply.

Indeed this plugin uses the Advanced Installer tool. As for the naming
scheme, it would not be accurate to add the msi word in the naming
scheme.
The tools builds all types of setups (MSI, EXE, APPV, APPX, etc). I feat it
would be misleading.
Thanks

On Tuesday, March 24, 2015 at 8:55:41 AM UTC+2, Christopher wrote:

Regarding the (as-yet undocumented) purpose, I guess the plugin is for
this generically-named piece of software:
http://www.advancedinstaller.com/

Maybe advanced-installer-msi-builder would be a slightly more helpful
and informative plugin ID?

-Chris

On 23/03/15 23:48, Oleg Nenashev wrote:
As I see, the plugin does not exist in your repo.
Could you clarify the purpose of the plugin (e.g. describe the use-case
in details)? There're many plugins, which may address your use-case. As
example, Custom Tools allows to setup an environment for builds.

вторник, 24 марта 2015 г., 9:27:51 UTC+3 пользователь advinst caphyon
написал:

Hello

I would like to request to host a Jenkins CI plugin for building
setups using Advanced Installer

Characteristics of plugin:
- Plugin will add a build step allowing setup builds using Advanced
Installer.

INFORMATION REQUESTED

*GitHub plugin name* : advancedinstaller-plugin

*Personal GitHub ID* : advinst

Thanks!

https://groups.google.com/d/msgid/jenkinsci-dev/3df34168-d39d-41d9-b9db-4258d2e697a3%40googlegroups.com

https://groups.google.com/d/msgid/jenkinsci-dev/3df34168-d39d-41d9-b9db-4258d2e697a3%40googlegroups.com?utm_medium=emailutm_source=footer.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/d0295877-670b-49df-b5a0-a471f50d278b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin hosting request: AdvancedInstaller Plugin

2015-03-24 Thread advinst caphyon

 


 
 Hello

I would like to request to host a Jenkins CI plugin for building setups 
using Advanced Installer

Characteristics of plugin:
- Plugin will add a build step allowing  setup builds using Advanced 
Installer.


INFORMATION REQUESTED
 
*GitHub plugin name* : advancedinstaller-plugin

*Personal GitHub ID* : advinst
 

Thanks!

-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/64ba0653-6aa1-4567-962e-7e5a19440cf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Hosting for Stash Pull Request Builder

2015-03-24 Thread domi

Done: https://github.com/jenkinsci/stash-pullrequest-builder-plugin
A component on the issue tracker is created too..
Please also make sure this is not valid information anymore:
https://github.com/nemccarthy/stash-pullrequest-builder-plugin/blob/dbff56b/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/stash/ApiTest.java#L9

btw. on the wiki, you don’t have to mention the minimal Jenkins Version and the
dependency to other plugins - this will be generated out of the pom.xml and
placed in the summery on top of the page as sonn as you released the first
version. Tshi way this information will be kept in sync.
/Domi

On 23 Mar 2015, at 09:33, Nathan McC nathan.e@gmail.com wrote:

Thanks. Updated the wiki with how to.

Would it be possible to get this into the jenkins ci on github to make this
official.

I'm assuming once I have a repo and permissions to do a relase the rest of
the info on the wiki page will populate.

On Monday, March 23, 2015 at 6:04:23 PM UTC+11, Dominik Bartholdi wrote:
Thats about the info I would expect on the plugins wiki page…
Domi

On 23 Mar 2015, at 01:24, Nathan McC nathan...@gmail.com wrote:

Add a blog post with some screenshots; http://blog.nemccarthy.me/?p=387

On Sunday, March 22, 2015 at 9:08:59 PM UTC+11, Nathan McC wrote:
Hey guys,

I've made a new Pull Request builder plugin for Stash, this plugin is
inspired by the GitHub and BitBucket PR builder plugins.

plugin name: stash-pullrequest-builder-plugin
github username: nemccarthy
github repo: https://github.com/nemccarthy/stash-pullrequest-builder-plugin

Wiki page;
https://wiki.jenkins-ci.org/display/JENKINS/Stash+pullrequest+builder+plugin

It would be awesome if I could get this one hosted.

Cheers,
Nathan

--
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-de...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/fb3a0eed-4bb7-4c07-a674-ace54f0c0ac7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/bc32495a-e3a0-4b7e-9689-ffa8377a6f7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/A8765EAF-355F-4FEB-BECD-707C28DC1EF8%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: AdvancedInstaller Plugin

2015-03-24 Thread Oleg Nenashev

As I see, the plugin does not exist in your repo.
Could you clarify the purpose of the plugin (e.g. describe the use-case in 
details)? There're many plugins, which may address your use-case. As 
example, Custom Tools allows to setup an environment for builds.

вторник, 24 марта 2015 г., 9:27:51 UTC+3 пользователь advinst caphyon 
написал:

  
  
  Hello

 I would like to request to host a Jenkins CI plugin for building setups 
 using Advanced Installer

 Characteristics of plugin:
 - Plugin will add a build step allowing  setup builds using Advanced 
 Installer.


 INFORMATION REQUESTED
  
 *GitHub plugin name* : advancedinstaller-plugin

 *Personal GitHub ID* : advinst
  

 Thanks!


-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3df34168-d39d-41d9-b9db-4258d2e697a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: AdvancedInstaller Plugin

2015-03-24 Thread advinst caphyon

Hi,

The plugin uses Advanced Installer Tool http://www.advancedinstaller.com/ to 
build setup files. It adds a build step which allows you to invoke the tool 
from command line and build a project file. 
Regarding the repo, I was under the impression that I should use the 
Jenkins repo. 

Thanks for the help.

As I see, the plugin does not exist in your repo.
 Could you clarify the purpose of the plugin (e.g. describe the use-case in 
 details)? There're many plugins, which may address your use-case. As 
 example, Custom Tools allows to setup an environment for builds.

 вторник, 24 марта 2015 г., 9:27:51 UTC+3 пользователь advinst caphyon 
 написал:

  
  
  Hello

 I would like to request to host a Jenkins CI plugin for building setups 
 using Advanced Installer

 Characteristics of plugin:
 - Plugin will add a build step allowing  setup builds using Advanced 
 Installer.


 INFORMATION REQUESTED
  
 *GitHub plugin name* : advancedinstaller-plugin

 *Personal GitHub ID* : advinst
  

 Thanks!



-- 
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d383bc2d-c799-4e1f-82a1-4588fa87c703%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

I don't share the opinion about the native packages being somehow not 
for real use or being unsupported.  Given that the packages are listed 
prominently on the home page, and no statement of install at your own 
risk; these are possibly broken is given, as a user I would have no 
reason to assume that the packages are not well supported.


It's a shame we don't have any download stats for the native packages.
At least on Debian (for people who have opted in to package tracking), 
there's fairly linear growth in package usage:

https://qa.debian.org/popcon-graph.php?packages=jenkins

The stats for Ubuntu look very similar.

Regards,
Chris


On 24/03/15 06:09, James Nord wrote:

I have always seen those packages as a convenience and never anything
that was to read into any supportability - especially given that they
don't (didn't) set dependencies correctly and install files to
completely inappropriate locations.  (there is a linux FHS for a reason).

So given that, my answer would be I don't care if CentOS 5 doesn't have
a JDK8 in its distribution packages as there is an RPM from Oracle if
people insist on doing it this way (which actually leads to a buggy
Jenkins install which miss-behaves in ways users don't expect!).  On top
of that the OpenJDK version 6 which ships with some OS'es that may
currently be used is buggy as hell, so anyone that uses that is just
asking for trouble at present.

/James

On Tuesday, 24 March 2015 10:58:07 UTC, Daniel Beck wrote:

How's availability of Java 8 (and preferably JDK 8 for the tools) on
the default package repos of the various platforms we have native
packages for?

On 24.03.2015, at 11:52, Stephen Connolly stephen.al...@gmail.com
javascript: wrote:

  Well jumping from Java 6 to Java 8 is a big jump. My point is
that we probably can strongly argue to jump to Java 7 today... then
in a few months (say 3 months after Java 7 is EOL... to allow for an
LTS that supports Java 7 but not Java 6) then we bump up to Java 8
 
  On 24 March 2015 at 10:41, nicolas de loof nicolas...@gmail.com
javascript: wrote:
  As said when I opened this topic, I can't see major benefit in
requiring Java 7 from a developer point of view (some syntactic
sugar, few new API, what else ?), compared to huge benefit of Java 8
to review API design and extensibility
 
  2015-03-24 11:36 GMT+01:00 Stephen Connolly
stephen.al...@gmail.com javascript::
  I think we could start looking at requiring Java 7 as a minimum
for Runtime of Jenkins... given that Maven 3.3.1 has moved its
minimum runtime to Java 7... if we want to bump the evil plugin
version to use the Maven 3.3.1 embedded jars we will have to bump
Jenkins to require Java 7 as a minimum... never mind that Java 7
goes EOL next month
 
  On 24 March 2015 at 10:33, James Nord james...@gmail.com
javascript: wrote:
  Rejoice! IBM AIX and z/OS now have a GA Java8 version.
 
  http://www-01.ibm.com/support/docview.wss?uid=swg21696670
http://www-01.ibm.com/support/docview.wss?uid=swg21696670
 
  Is it time to revisit this once more?
 
  /James
 
 
  On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote:
  On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite
mark.ea...@gmail.com wrote:
   I added a new test to the git client plugin which depended on a
Java 7 NIO
   feature.  It failed to compile in my test configuration with
Java 6.
 
  I think it is fine to require Java 7 in tests; there was already a
  proposal which met with no controversy to require 7 for building
  plugins, while continuing to use -target 6 and Animal Sniffer to
  prevent accidental use of 7+ APIs or bytecode (*). Requiring 8 for
  building plugins, and thus allowing -source 8 features in
  src/test/java/**/*.java (**), would be a natural next step, a bit
  controversial but much less so than requiring 8 for running Jenkins
  itself.
 
 
  (*) Of course this means functional tests do not find runtime
problems
  occurring on 6 despite lack of linkage errors. But the
alternative of
  running tests on 6 just means the reverse problem, that behavioral
  changes in 7 which break the plugin are not caught; and this is
worse,
  since many more people will really be running on 7.
 
  (**) The upcoming version of Animal Sniffer allows you to skip
checks
  on test-scope dependencies. But it might not yet allow checks to be
  skipped on src/test/java/**/*.java, which is not a dependency; will
  need to look into it.
 
  --
  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-de...@googlegroups.com javascript:.
  To view this discussion on the web

Re: Proposal : Jenkins to require Java 8

2015-03-24 20:59 GMT+01:00 Richard Bywater rich...@byh2o.com:

I'm sorry but yet again you appear to be taking a very rude attitude with
other community members with basically your opinion does not matter.

Last time I checked I was part of the *we* by being part of the community
and simply saying update your infrastructure trivialises the situation for
what is possibly a reasonable user base of Jenkins.

Java 7 is not even end of lifed yet and so I'm wondering what the
compelling argument for Java 8 is. That is, what features does it enable
that will drive Jenkins to the next level?

- Refactor API / extension points as @FunctionalInterface
- adopt closures vs anonymous classes
- replace abstract class extension mechanism with interface (and as such
multi-inheritance support)
- + few new useful APIs

Richard

On 8:53AM, Wed, 25/03/2015 Kanstantsin Shautsou kanstantsin@gmail.com
wrote:

On Mar 24, 2015, at 22:37, Richard Bywater rich...@byh2o.com wrote:

Richard.

On Wed, 25 Mar 2015 at 08:07 Jesse Glick jgl...@cloudbees.com wrote:

On Tue, Mar 24, 2015 at 6:41 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
I can't see major benefit in requiring Java 7 from a developer point
of view (some syntactic sugar, few new API

java.nio.file.* is actually rather important for Jenkins code,
particularly in core, since it uses the filesystem so heavily.

--
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 discussion on the web visit https://groups.google.com/d/
msgid/jenkinsci-dev/CANfRfr1%2BwP_j6S7_RtoLH_SYTjdO8Bs-
QxEod520hhe5xKv7AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to a topic in the
Google Groups Jenkins Developers group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui9471xSn_NknofC4H%2BaScs_j7oi%2B%2BpJcvEsz59CYgX81jdA%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui9471xSn_NknofC4H%2BaScs_j7oi%2B%2BpJcvEsz59CYgX81jdA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/2EDF677B-14F1-478C-A2D5-4BC1514AAB06%40gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/2EDF677B-14F1-478C-A2D5-4BC1514AAB06%40gmail.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947O1Bfx%2Bf%2B%2BL3U%2BsfYnBnqMJqUkS5oRSf-dhNbTcFs5ZA%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947O1Bfx%2Bf%2B%2BL3U%2BsfYnBnqMJqUkS5oRSf-dhNbTcFs5ZA%40mail.gmail.com?utm_medium=emailutm_source=footer
.

For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzkOu43h5Qw3pNq5%2BQtfoyByv8C0FQZSk84Fde4vUgnSnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

Yeah, since we're upgrading, it may as well be to Java 8 since it (seems 
to be) be available for every OS we package for, and it would minimise 
the pain for users, rather than splitting it across two updates.


I don't think we specify the required Java version in most of our native 
package specs, and WAR users upgrading will have no way of knowing about 
the Java requirement change, so we probably need to do a lot of user 
education in advance.


Maybe we can have banners inside the web interface for one or two 
releases in advance, warning about the impending Java version 
requirement?  Plus big red text in the changelog, articles on the blog, 
Twitter etc.


Some banners on the website, wiki and issue tracker (as we sometimes do, 
e.g. for donation or JUC advertising) would also be a good idea.


Regards,
Chris


On 24/09/14 12:40, Baptiste Mathus wrote:

I'm absolutely +1 on the advantages on the programming model that
defining a JDK8 as a minimum JDK would give us. And like Nicolas, I also
think JDK7 is not really worth it as 8 is.

And Jenkins is one of those tools that has somehow a lower barrier on
that requirement upgrade, since for example the build JDK can a totally
different one, or wouldn't impact say a ruby/C/whatever compiler anyway.

Btw, I guess we own at least of those AIX installs, and JDK are actually
generally not so that behind. JDK8 for AIX seems to be not GA *yet* but
I'm sure IBM is working on it if not already out (found
http://www.ibm.com/developerworks/java/jdk/beta/ for example).
Sure, old platform like AIX 4 or 5.x wouldn't have those JDK supported,
so I suppose there could be some Jenkins VeryLTS to keep Java 6 as it's
now for say some months or even a year for only very important issues.
That would give time for those platform a bit more time to provide the
JDK8 port/version for their OS.

2014-09-24 19:42 GMT+02:00 Daniel Beck m...@beckweb.net
mailto:m...@beckweb.net:


On 24.09.2014, at 11:48, Martin Kutter martin.kut...@fen-net.de
mailto:martin.kut...@fen-net.de wrote:

 Just want to throw in that java 8 is not yet available on all platforms
 (like AIX, HP-UX and probably some other less frequently used commercial
 UNIXes).

I checked the anonymous usage stats a few weeks ago:
Out of 93,400 installs, we know the master's OS for 85,200 of them.
285 are AIX. 120 are HP-UX. 50 installs total on OpenBSD, Darwin,
OS/400, z/OS and NetBSD.

Not relevant enough IMO if the advantages are significant.

I can provide the queries I used if anyone wants to verify these.

--
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
mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!

--
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
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 discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5511CD16.6090302%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

I think jenkins can check java version on startup and print friendly message to
log instead of some java related stacktraces.

On Mar 24, 2015, at 23:46, Christopher Orr ch...@orr.me.uk wrote:

Yeah, since we're upgrading, it may as well be to Java 8 since it (seems to
be) be available for every OS we package for, and it would minimise the pain
for users, rather than splitting it across two updates.

I don't think we specify the required Java version in most of our native
package specs, and WAR users upgrading will have no way of knowing about the
Java requirement change, so we probably need to do a lot of user education in
advance.

Maybe we can have banners inside the web interface for one or two releases in
advance, warning about the impending Java version requirement? Plus big red
text in the changelog, articles on the blog, Twitter etc.

Some banners on the website, wiki and issue tracker (as we sometimes do, e.g.
for donation or JUC advertising) would also be a good idea.

Regards,
Chris

On 24/09/14 12:40, Baptiste Mathus wrote:
I'm absolutely +1 on the advantages on the programming model that
defining a JDK8 as a minimum JDK would give us. And like Nicolas, I also
think JDK7 is not really worth it as 8 is.

And Jenkins is one of those tools that has somehow a lower barrier on
that requirement upgrade, since for example the build JDK can a totally
different one, or wouldn't impact say a ruby/C/whatever compiler anyway.

Btw, I guess we own at least of those AIX installs, and JDK are actually
generally not so that behind. JDK8 for AIX seems to be not GA *yet* but
I'm sure IBM is working on it if not already out (found
http://www.ibm.com/developerworks/java/jdk/beta/ for example).
Sure, old platform like AIX 4 or 5.x wouldn't have those JDK supported,
so I suppose there could be some Jenkins VeryLTS to keep Java 6 as it's
now for say some months or even a year for only very important issues.
That would give time for those platform a bit more time to provide the
JDK8 port/version for their OS.

2014-09-24 19:42 GMT+02:00 Daniel Beck m...@beckweb.net
mailto:m...@beckweb.net:

On 24.09.2014, at 11:48, Martin Kutter martin.kut...@fen-net.de
mailto:martin.kut...@fen-net.de wrote:

Just want to throw in that java 8 is not yet available on all platforms
(like AIX, HP-UX and probably some other less frequently used commercial
UNIXes).

I checked the anonymous usage stats a few weeks ago:
Out of 93,400 installs, we know the master's OS for 85,200 of them.
285 are AIX. 120 are HP-UX. 50 installs total on OpenBSD, Darwin,
OS/400, z/OS and NetBSD.

Not relevant enough IMO if the advantages are significant.

I can provide the queries I used if anyone wants to verify these.

--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!

--
You received this message because you are subscribed to a topic in the Google
Groups Jenkins Developers group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/sw_WepGw0Pk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/5511CD16.6090302%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/DFB272E0-689A-4170-AF22-C321B7FE7431%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

On 24.03.2015, at 20:53, Kanstantsin Shautsou kanstantsin@gmail.com wrote:

The problem with the Java version used to run Jenkins is that it needs to be
available on whatever box your builds run on.

It's nice if you're only building products using the latest hype technology,
and discard them as soon as they're done, or upgrade the technology stack in
every iteration, but there are *many* companies that still need to maintain
products originally developed a decade or more ago, and the tools to build them
are just as old, and wouldn't properly run on current systems.

And it's simply not possible to update Jenkins (master) in isolation, the
remoting model requires that all slaves use similar JREs, and satisfy the
minimum requirements.

Ok, s/we/imho/ . Btw, there should be somewhere statistics. Let’s check how
many RHEL5 installation jenkins has.

If you're referring to the anonymous usage statistics, we only know that
they're running Linux, and the CPU architecture (os.name and os.arch).

And again, it's likely not the installations of Jenkins (i.e. master) that
are the problem, but the build nodes.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/25005053-52C1-4F40-B722-2A69E5A64F4D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8

What prevent you to get JDK8 on slave to run the remoting agent, but use
JDK installer to build your legacy JDK 1.1 application ?

2015-03-24 21:57 GMT+01:00 Daniel Beck m...@beckweb.net:

On 24.03.2015, at 20:53, Kanstantsin Shautsou kanstantsin@gmail.com
wrote:

The problem with the Java version used to run Jenkins is that it needs to
be available on whatever box your builds run on.

It's nice if you're only building products using the latest hype
technology, and discard them as soon as they're done, or upgrade the
technology stack in every iteration, but there are *many* companies that
still need to maintain products originally developed a decade or more ago,
and the tools to build them are just as old, and wouldn't properly run on
current systems.

And it's simply not possible to update Jenkins (master) in isolation, the
remoting model requires that all slaves use similar JREs, and satisfy the
minimum requirements.

Ok, s/we/imho/ . Btw, there should be somewhere statistics. Let’s check
how many RHEL5 installation jenkins has.

If you're referring to the anonymous usage statistics, we only know that
they're running Linux, and the CPU architecture (os.name and os.arch).

And again, it's likely not the installations of Jenkins (i.e. master)
that are the problem, but the build nodes.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/25005053-52C1-4F40-B722-2A69E5A64F4D%40beckweb.net
.
For more options, visit https://groups.google.com/d/optout.

--
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 discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmtvFmMnMki7q6H-0NDLmsQVjuzuC2xexvc0hb204iCaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal : Jenkins to require Java 8