Reindex failure due to OOME caused a problem. I rerun it to the completion
and things are now back to normal.
2013/12/11 Jesse Glick
> Is it just me or is JIRA now devoid of any issues except in the cvs
> component? Unless you directly link to them? All searches come up
> empty (except in cvs).
On Wed, Dec 11, 2013 at 5:02 PM, Daniel Beck wrote:
> whether plugin authors would be able to specify a minimum Jenkins version in
> a way that works for 1.532.x and doesn't break 1.533-1.536
There is no way to do it for sure, but we generally punt on the issue
and say that if you declare a 1.53
Oliver,
the following issues don't qualify (yet) as they're either
features/improvements, or too recent. But all of the changes are quite small,
and improve security, so it might be a good idea backport them anyway:
- JENKINS-20800 (since 1.543): Log messages aren't escaped on the UI. Relevant
Hi,
I would like to release (or have someone else release ;) a new version of
the parameterized trigger plugin. I am especially interested in having the
commit
https://github.com/jenkinsci/parameterized-trigger-plugin/commit/bb32d967c9182281898b871c13dcb37b838c8082released.
If there are no obje
Looks like JIRA was nearing OOM error and the e-mails were clogging in
the queue. I just restarted the instance and all the e-mails have been
flushed.
On 12/11/2013 10:51 AM, Kohsuke Kawaguchi wrote:
Looking into this now.
On 12/11/2013 07:47 AM, Larry Shatzer, Jr. wrote:
I've also notice
Hi,
The weblogic-deployer plugin has "vanished" from the JIRA for a while. Anyone
can tell me why ? Do I have to update plugin wiki page ?
Thanks
Regards,
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group
Yes, but it's not listing all CVS issues, just the 2 I've just updated.
On 11 December 2013 19:14, Jesse Glick wrote:
> Is it just me or is JIRA now devoid of any issues except in the cvs
> component? Unless you directly link to them? All searches come up
> empty (except in cvs).
>
> --
> You r
Is it just me or is JIRA now devoid of any issues except in the cvs
component? Unless you directly link to them? All searches come up
empty (except in cvs).
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and
Looking into this now.
On 12/11/2013 07:47 AM, Larry Shatzer, Jr. wrote:
I've also noticed the Jenkins Issues mailing list has not had any updates
either. Just spam from the last few days (I'm not a moderator there to clean it
up)...
On Fri, Dec 6, 2013 at 8:34 AM, Larry Shatzer, Jr. mailto:l
Hi,
I have started backporting changes for 1.532.2[1].
[1]
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.532.2-fixed%22
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsub
Hello,
I think the claim plugin provides the feature you are looking for.
HTH
Le 11 déc. 2013 13:34, "Otto P" a écrit :
> Pardon if this has been answered before.
>
> I am looking for a way to manually annotate test results.
>
> The use case: suppose a test fails. You analyze the root cause. Th
sorry trigger happy that should read "from an earlier post 2.10.1 release
(aka 2.10.2-snapshot)"
On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
>
> Not sure this is still the case (as its from an early post but the plugins
> assumptions about project types appears incorrect and result
Not sure this is still the case (as its from an early post but the plugins
assumptions about project types appears incorrect and results in the
following error
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException:
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/class
I've also noticed the Jenkins Issues mailing list has not had any updates
either. Just spam from the last few days (I'm not a moderator there to
clean it up)...
On Fri, Dec 6, 2013 at 8:34 AM, Larry Shatzer, Jr. wrote:
> I've gotten 2, but missed a bunch of others I expected to get. Is the mail
I have a multijob phase with two jobs. I added condition "Mark phase as
successful" when "Successful", But when one job fails it is not stopping
another job. Simply coming out and executing post-build actions. How can i
stop remaining jobs completely when one job failed in same phase?
--
View th
Ok everything seems to be working :)
Thank you
On Wednesday, December 11, 2013 3:31:00 PM UTC+1, Ullrich Hafner wrote:
>
>
> Am 11.12.2013 um 13:45 schrieb robin.jarry
> >:
>
> Awesome thanks !
>
> my github username: robin-jarry
>
>
> Ok, you should now have commit rights.
>
> Do we need to pus
Am 11.12.2013 um 13:45 schrieb robin.jarry :
> Awesome thanks !
>
> my github username: robin-jarry
>
Ok, you should now have commit rights.
> Do we need to push all our commits on the fork on jenkinsci from now on ?
Yes.
>
> On Wednesday, December 11, 2013 1:25:17 PM UTC+1, Ullrich Hafne
Awesome thanks !
my github username: robin-jarry
Do we need to push all our commits on the fork on jenkinsci from now on ?
On Wednesday, December 11, 2013 1:25:17 PM UTC+1, Ullrich Hafner wrote:
>
> Created https://github.com/jenkinsci/lockable-resources-plugin
>
> What is your github user name?
Pardon if this has been answered before.
I am looking for a way to manually annotate test results.
The use case: suppose a test fails. You analyze the root cause. The problem
is not trivially fixed. So you want to capture your findings somewhere -
other than a sticky note or a vague discussio
Created https://github.com/jenkinsci/lockable-resources-plugin
What is your github user name?
Ulli
Am 11.12.2013 um 13:18 schrieb robin.jarry :
> Gentle bump :-)
>
> On Monday, December 9, 2013 4:25:51 PM UTC+1, robin.jarry wrote:
> Yes I already looked at this plugin but with I found some lim
Gentle bump :-)
On Monday, December 9, 2013 4:25:51 PM UTC+1, robin.jarry wrote:
>
> Yes I already looked at this plugin but with I found some limitations
> (which I'm not sure can be worked around):
>
>- It doesn't seem possible to schedule several builds of the same
>projects while all
Wouldn’t it make more sense to add your core portlets to the dashboard view
plug-in and add your sonar portlets to the sonar plugin?
Ull
Am 11.12.2013 um 03:24 schrieb Georg Henzler :
> Hi all,
>
> I've created additional dashboard portlets to extend the
> https://wiki.jenkins-ci.org/display
I second that.
We have 99% parameterized builds with an average of 12 parameters each. Some of
them are dependand to each other (example: iOS Dev: mobile provisioning profile
+ code signing identity + bundle identifier).
So when selecting a certain value from a dropbox, other dropboxes should cha
23 matches
Mail list logo
