It is being really funky. I requested a password reset days ago and never got
it. Then this morning I tried requesting with my email instead of username and
it came after a few minutes.
Then just now I got the one from yesterday. Looking at the headers it appears
to be getting stuck inside
then would significantly limit the available implementations. Maybe then we
could cancel the Run, as we run early in it's lifecycle, and re-schedule it as
a task in the Queue, claiming the Run never existed ?
2016-03-09 21:40 GMT+01:00 Jesse Glick
<jgl...@cloudbees.com<mailto:jgl...@cloudbees.c
On 3/9/16, 12:40 PM, "jenkinsci-dev@googlegroups.com on behalf of Jesse
Glick"
wrote:
>
>Or just fail the build and the next one should work.
I just don't want to have to kick builds when a normal slave would "just
wait". Our
Not being an iCLA signer I have experienced the loop of death and that’s fine.
I do not however wish it on iCLA signers.
Would an acceptable compromise be that people with push access are allowed to
optionally "skip" the human review portion of the PR? It would still require
that Jenkins is
I like that this moves the provisioning to the build log.
I do agree that certain issues should fail immediately (image not found).
Certain other issues should perform exponential backoff (Cloud infrastructure
down). Provisioning limits could be annoying though, would be interesting if
they
What about a screen in Jenkins Admin that lists all the "breaking"
security fixes since the release of the LTS. By default after an update
any new security fixes are in "Unacknowledged mode". Having any
unacknowledged items adds a banner to the entire application.
You can then either "Accept the
I've never tried it with a large meeting, but maybe it is worth trying
https://talky.io/ ?
-
Thomas
On 7/29/15, 12:56 PM, jenkinsci-dev@googlegroups.com on behalf of Daniel
Beck jenkinsci-dev@googlegroups.com on behalf of m...@beckweb.net wrote:
On 29.07.2015, at 20:12, Manuel Jesús Recena
Nevermind, working now.
From: Thomas Suckow thomas.suc...@pnnl.govmailto:thomas.suc...@pnnl.gov
Subject: Re: UI changes branch progress report Day 1
Getting The party is over
From: jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com
Subject: UI changes branch progress report Day
You need a plugin like xUnit. Then you need to configure karma to output in a
format it understands. I have traditionally saved all test output in junit
format
From: Erick Macedo erickfmac...@gmail.commailto:erickfmac...@gmail.com
Reply-To:
Also, don't cross post. This should have only been asked on the jenkins-users
list.
From: Erick Macedo erickfmac...@gmail.commailto:erickfmac...@gmail.com
Reply-To:
jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com
The changelog li's should really have /li, instead the browser has to figure
it out
Just a thought...
-
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
I did not know that.
I am going to pretend today is Monday and shut up now.
-
Thomas
On 5/26/15, 10:38 AM, Daniel Beck m...@beckweb.net wrote:
On 26.05.2015, at 17:58, Suckow, Thomas J thomas.suc...@pnnl.gov wrote:
The changelog li's should really have /li, instead the browser has
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
I was hoping someone could critique my pull request for core. I am perplexed by
the unit test failing as it succeeds on my system. I can't figure out how my
test differs from some of the other similar tests.
I would also appreciate any critiques in general that would make this a better
PR.
You probably need -X POST
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API
From: Vinoth raj vinoth@gmail.commailto:vinoth@gmail.com
Reply-To:
jenkinsci-dev@googlegroups.commailto:jenkinsci-dev@googlegroups.com
Dear all,
I am trying to figure out the best way to get a pull request accepted. This is
a very community run organization and as such there are many updates and weekly
releases. Though it appears (with the exception of translations) the last month
has been only people with commiter access get
18, 2015, Suckow, Thomas J
thomas.suc...@pnnl.govmailto:thomas.suc...@pnnl.gov wrote:
Alright, I have made a pull request resolving a number of label equality
issues.
https://github.com/jenkinsci/jenkins/pull/1569
Should I make a formal JIRA issue and cross reference them?
Yes
-
Thomas
On 2/18
, Suckow, Thomas J thomas.suc...@pnnl.gov
wrote:
The question becomes, are Labels singletons? Do I make a PR changing ==
to equals?
Should use equals(), as implied by the comment on Jenkins.labels and
the existing of the equals override.
--
You received this message because you are subscribed
Looking into this further I come across this interesting nugget:
println(
Jenkins.getInstance().unlabeledNodeProvisioner.stat.computeQueueLength() )
println( Label.get(mylabel).nodeProvisioner.stat.computeQueueLength() )
Gives:
1
0
Meaning, it is on a queue as unlabeled. Yet, the only job in
I have come across an issue where Queue uses == to compare Labels. This is fine
if they are truly singletons. However, somehow [and I don't know why] I am
getting an item in the queue with a Label that is not a singleton.
The question becomes, are Labels singletons? Do I make a PR changing ==
The erroneous 1 is caused by a change in 2013.
https://github.com/jenkinsci/jenkins/pull/742
Now to track down the 0.
-
Thomas
On 2/9/15, 9:44 AM, Suckow, Thomas J thomas.suc...@pnnl.gov wrote:
Looking into this further I come across this interesting nugget:
println(
Jenkins.getInstance
I am not convinced that the durable task plugin is to blame.
I am seeing a long line of:
FINE hudson.slaves.NodeProvisioner
Queue length 0 is less than the idle capacity 0. No provisioning strategy
required
Yet I have 8 jobs in the build queue. Something is afoot. I'l keep digging when
I
Even with an up-to-date durable-task plugin, it happened again :(
I pulled the thread stack traces with the queued builds not building and then
restarted jenkins. Comparing the threads, they are nearly identical.
I've added fine logging for the NodeProvisioner, hopefully that will show
I have updated it. So far I haven't seen the issue, but the job also does not
often get triggered. I'll keep an eye on it.
From: Nigel Magnay
The API is certainly problematic. For example, on the latest in-dev versions, I
can generate (occasionally) a deadlock.
You may wish to try upgrading
25 matches
Mail list logo