After I have managed to set up my environment for Jenkins development, I
started to implement a test case for the problem in
test/hudson/tasks/ArtifactArchiverTest.java. I have attached the file. The
test seems to work fine, but I am unhappy with some details. Maybe you have
some hints for me?
On Wednesday, 25 March 2015 16:33:09 UTC, Jesse Glick wrote:
On Wed, Mar 25, 2015 at 6:53 AM, Stephen Connolly
stephen.al...@gmail.com javascript: wrote:
Which is why I think going for JDK7 now is a better plan than trying to
jump
all the way to JDK8
Painful as it is, I tend to
Not entirely true - Redhat customers will get until at least November (so a
further 6 months) and even after that the company could be paying Oracle
for extended support.
Richard.
On Thu, 26 Mar 2015 at 22:39 James Nord jamestn...@gmail.com wrote:
On Wednesday, 25 March 2015 16:33:09 UTC,
You misread and 100% agreed with what I originally said :-)
...they will have a JDK that won't get security fixes in less time than
this* unless they have some commercial support*
Getting fixes from RedHat requires an active licence/support agreement,
ditto for Java SE for business.
On
right, so the JDK 7 EOL mostly doesn't match our next LTS,
so as we know a JDK switch will impact users, I suggest we postpone JDK
upgrade to post-may LTS, then can adopt JDK 8 in June so the LTS we will
select in July can be based on it.
Doing this, we will only enforce jenkins user to upgrade
Hello,
This plugin enables a project to trigger itself recursively after a delay,
the delay can be configured while creating the project.
GitHub plugin name : selfie
GitHub ID : abhirama
GitHub repository : https://github.com/abhirama/selfie
Cheers,
Abhi
--
You received this
On 26 March 2015 at 12:06, nicolas de loof nicolas.del...@gmail.com wrote:
2015-03-26 12:57 GMT+01:00 James Nord jamestn...@gmail.com:
Nicolas, your logic is not correct in that we only force users to upgrade
once.
Just because we would require JDK7 does not mean the user needs to
2015-03-26 12:57 GMT+01:00 James Nord jamestn...@gmail.com:
Nicolas, your logic is not correct in that we only force users to upgrade
once.
Just because we would require JDK7 does not mean the user needs to install
JDK7 and then JDK8 when we require JDK8. They can (*if their platform
Get back to us when you have one that actually building
On 26 March 2015 at 12:15, nicolas de loof nicolas.del...@gmail.com wrote:
2015-03-26 12:55 GMT+01:00 Stephen Connolly
stephen.alan.conno...@gmail.com:
I'm going to try the code walks approach here is my suggestion
PR failed ;)
On Mar 26, 2015, at 15:15, nicolas de loof nicolas.del...@gmail.com wrote:
2015-03-26 12:55 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com
mailto:stephen.alan.conno...@gmail.com:
I'm going to try the code walks approach here is my suggestion
On 26 March 2015 at 09:39, James Nord jamestn...@gmail.com wrote:
On Wednesday, 25 March 2015 16:33:09 UTC, Jesse Glick wrote:
On Wed, Mar 25, 2015 at 6:53 AM, Stephen Connolly
stephen.al...@gmail.com wrote:
Which is why I think going for JDK7 now is a better plan than trying to
jump
all
2015-03-26 12:55 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com
:
I'm going to try the code walks approach here is my suggestion
https://github.com/jenkinsci/jenkins/pull/1624
I'm sure that nicolas will complain about that one
indeed
here is mine
I'm going to try the code walks approach here is my suggestion
https://github.com/jenkinsci/jenkins/pull/1624
I'm sure that nicolas will complain about that one
On 26 March 2015 at 10:55, nicolas de loof nicolas.del...@gmail.com wrote:
right, so the JDK 7 EOL mostly doesn't match our next
Nicolas, your logic is not correct in that we only force users to upgrade
once.
Just because we would require JDK7 does not mean the user needs to
install JDK7 and then JDK8 when we require JDK8. They can (*if their
platform supports it*) install JDK8 straight away and run Jenkins
Hi,
whether it is possible to have nested view plugin showed status during the
build?
I'm talking about the status of In progress - flashing ball red/green.
At the moment - static ball.. I tried to modify the plugin, but without
any interesting effects..
Any ideas?
--
You received this
hi, i'm wondering if anyone here might be able to comment of the
feasibility of the following:
I'm trying to build a jenkins plugin in order to assist with our
release/deployment process.
in order to do this i want to retrieve parameters from a different job and
present these to a user in the
i am using MSbuild plugin to deploy the application,Everything is working
fine ,but website is mapping to inetpub/wwwroot.Here my requirement is i
need to map the website to physical path c:\xxx.Please fidn the below
information and suggest me the solution.thanks in advance.
what is the
I've done some work to move the Token Macro plugin to use Run instead of
AbstractBuild for the workflow plugin stuff. Please take a look and
comment on https://github.com/jenkinsci/token-macro-plugin/pull/16
--
You received this message because you are subscribed to the Google Groups
Jenkins
Hi, any update on this? I've updated the project description at github.
thanks.
On Wednesday, March 25, 2015 at 9:27:38 PM UTC-6, Alexis Tejeda wrote:
Dear Jenkins
Here is the needed info to host a plugin
- your GitHub plugin name: *almasw-modbuilder-plugin*
- your personal GitHub
So is there anything else I can do to get approved, otherwise I would need
the reason for denial so I can give something to my superiors.
Regards
On Thursday, March 12, 2015 at 8:13:14 AM UTC+1, Christopher wrote:
Hi there,
Can you please provide some information about this tool?
I
On Thu, Mar 26, 2015 at 8:19 AM, Adam Scarborough scar...@gmail.com wrote:
1) create a drop down consisting of a listing all jobs currently in jenkins
(i beleive this is reasonably trivial)
2) dependent on what is selected in that drop down display another drop down
consisting of the
Hi,
I have a builder with two drop-down lists(DDL). DDL's are filled via
descriptor, which is singleton instance.
I follow steps:
1. Create 2 or more jobs;
2. Change one DDL value in 1st job.
Expected result: the same value in other jobs is untouched.
Actual result: the same value in other jobs
On Thu, Mar 26, 2015 at 5:39 AM, James Nord jamestn...@gmail.com wrote:
switching the baseline to Java 8 means that someone whose corporate IT
supports installation of only Java 7 will not receive even security
fixes in about three months.
But they will have a JDK that won't get security
23 matches
Mail list logo
