Thanks guys!
Was a problem with it only updating snapshots which I found in the wiki.
Its released now successfully, just need to wait for the update. Thanks for
the help.
On Tuesday, March 24, 2015 at 7:58:29 PM UTC+11, Daniel Beck wrote:
Uploaded ten minutes after Richard linked to the
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
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
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
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
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
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
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
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
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
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,
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
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
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:
Well jumping from Java 6 to Java 8 is a big jump. My point is
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:
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,
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...
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
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,
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
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
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
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
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
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
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!
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
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.
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
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,
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
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
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
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
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
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.
--
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
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
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
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
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
+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
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.
On Mar 24, 2015, at 22:37, Richard Bywater
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
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:
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
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
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:
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
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
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
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
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
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
On 24.03.2015, at 20:53, Kanstantsin Shautsou kanstantsin@gmail.com wrote:
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
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:
Sorry, but rhel5 is not
On 24.03.2015, at 21:57, nicolas de loof nicolas.del...@gmail.com wrote:
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 ?
The Maven Job Type :-)
Seriously though, is JDK 8 available for all platforms we
Are you possibly hitting the first issue described at
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues
?
Richard
On Tue, 24 Mar 2015 at 21:29 Nathan McC nathan.e@gmail.com wrote:
Ok so setting the username and password in settings.xml
Ok so setting the username and password in settings.xml seems to have
solved the error. Now I just dont set username or password.
The release is successful according to maven command line. The problem now
is that nothing seems to be appearing in
This is it isn't it?
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/stash-pullrequest-builder/
On Tue, Mar 24, 2015 at 1:29 AM, Nathan McC nathan.e@gmail.com wrote:
Ok so setting the username and password in settings.xml seems to have solved
the error. Now I just dont set
Uploaded ten minutes after Richard linked to the wiki.
And here are the failed releases:
http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/stash-pullrequest-builder/1.0.0-SNAPSHOT/
On 24.03.2015, at 09:52, Benjamin Lau benjamin.a@gmail.com wrote:
This is it isn't it?
https://github.com/jenkinsci/flaky-test-handler-plugin/pull/1
Critical fix, no response from maintainer for over a month.
--
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,
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
Ok, s/we/imho/ . Btw, there should be somewhere statistics. Let’s check how
many RHEL5 installation jenkins has.
On Mar 24, 2015, at 22:59, Richard Bywater rich...@byh2o.com wrote:
I'm sorry but yet again you appear to be taking a very rude attitude with
other community members with
Yes, each class has a nested descriptor class.
I did a clean and then a rebuild and that seems to magically have fixed
things.
-- Greg
On 03/24/2015 01:24 PM, Ulli Hafner wrote:
Did you provide 2 descriptors?
Am 24.03.2015 um 14:39 schrieb Greg Allen gal...@redhat.com:
I have a plugin
Oops, yeah its just a test account.
Thanks for creating a repo. Having some problems with the release process.
Running /bin/sh -c cd
/Users/nathan/DEV/ECO/bitbucket-pullrequest-builder-plugin git push
ssh://nemccarthy:passw...@github.com/jenkinsci/stash-pullrequest-builder-plugin.git
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
I know projects that uses ancient distros and the root problem is that they
didn’t schedule/plan upgrades in time at all. They don’t want to do it and it
easy for them to slow down any projects they want. I think CloudBees will be a
good company for doing payed support for ancient platforms. I
So another idea that “update button” should compare and warn about java
versions if they planned to be changed :)
On Mar 25, 2015, at 00:03, Christopher Orr ch...@orr.me.uk wrote:
I don't actually know how the startup / WAR extraction stuff works, but I did
wonder whether a Java
Java 7 will be a good first move.
Add Java 8 is requirement roadmap for say, 6 months, time for CI teams to
prepare themselves.
On Linux and Windows, it's easy to have Java 8, it's another story on older
hardware/OS.
I would also suggest keep slave.jar Java 6 or 7 to make slaves running on
This is not just slave.jar, all callable serialized and sent to slave need
to rely on same class format, so you can't keep slave 1.6 compatible
2015-03-24 22:15 GMT+01:00 Henri Gomez henri.go...@gmail.com:
Java 7 will be a good first move.
Add Java 8 is requirement roadmap for say, 6 months,
71 matches
Mail list logo
