Hi,
Please use the Jenkins Users mailing list instead of this one
Cheers
On Thursday, 7 January 2016 08:54:38 UTC+1, SAI KIRAN wrote:
>
>
> Hi,
>
> I am trying to run a suite in Jenkins and update those test results in ALM
> (Pass/Fail)
>
> But, I am unable to update to ALM.
>
>
>
> Which lo
Hi,
I had the same problem yesterday. Is your job running on a slave? Digging
in the sourcecode of the plugin, I found out, that it is looking for the
test results in the job directory on the master instead of the workspace on
the slave. Archiving the testresults in a previous post build action wa
I'm trying to write my first plugin, so apologies for the probably very
obvious questions.
I'm trying to extend FreeStyleProject so that I can override the
'getIconColor' method with some custom functionality (currently just sets it
to 'Not built' for testing but will be doing more later). My cur
I guess it should be quite easy to write a plugin with a CliCommand that
just calls Run.writeWholeLogTo.
/B
On Thu, Jan 7, 2016 at 2:38 AM, Greg Mattson wrote:
> All,
>
> I'd very much like to take the monitoring of my jenkins processes into the
> shell:
>
> 1. ability to attach to a tmux sessi
Cool idea!
I'm just sad that gmail doesn't provide me with means of filtering on mail
headers so these requests will unfortunately be lost in the rest of the
GitHub updates that I get. Unless someone with more gmail filter foo has
any tips for me.
/B
On Thu, Jan 7, 2016 at 5:08 AM, Michael Neale
I've updated https://github.com/jenkinsci/git-client-plugin/pull/196 to
request review of a fix for a regression introduced in the most recent
release of the git client plugin. I'm looking forward to feedback.
Mark Waite
On Thu, Jan 7, 2016 at 4:39 AM Robert Sandell
wrote:
> Cool idea!
> I'm j
It seems that two changes
(https://github.com/search?utf8=%E2%9C%93&q=JacocoBuildAction+getOwner+user%3Ajenkinsci&type=Code&ref=searchresults)
and
(https://github.com/search?utf8=%E2%9C%93&q=JacocoBuildAction+owner+user%3Ajenkinsci&type=Code&ref=searchresults)
related to owner
So I would sa
Hi Robert,
Glad you like it. Depends on what you want to filter on, if you mean on the
fact that @jenkinsci/code-reviewers alias was target, that info does indeed
not seem to be in the email.
But seems like you can use some wildcards and so on.
Like : list:(jenkins*.github.com) to filter for ev
I don't really know the full extent of what you are trying to achieve, but
I wouldn't get down the road of writing a new kind of project 'just' for
this.
If it is about swapping some icons depending on an custom criteria, I'd
take a look at https://github.com/jenkinsci/greenballs-plugin and build
Is there a known workaround for this bouncycastle conflict? I just ran into
this issue as I try to use mock-server to write a unit test for the
http-request-plugin.
On Friday, March 21, 2014 at 10:23:08 AM UTC-4, Jesse Glick wrote:
>
> On Fri, Mar 21, 2014 at 10:19 AM, Jesse Glick > wrote:
> >
That looks like a potential alternative solution. I will suggest that to my
team. We do like having a single build for all branches though as we have a
lot of builds and multiplying this by the number of branches isn't ideal.
It would still be nice to solve this problem in case I need to work on o
On 07.01.2016, at 12:39, Robert Sandell wrote:
> Unless someone with more gmail filter foo has any tips for me.
All such notifications will contain the string @jenkinsci/code-reviewers in the
body that you can filter for (or exclude from the existing filter that hides
GitHub notifications).
Hi,
A question such as this should be in the Jenkins Users mailing list, it's
worth if you don't duplicate it everwhere, as you already raised that
question in that group e
Cheers
On Thursday, 7 January 2016 11:58:31 UTC+1, donovan.b...@gmail.com wrote:
>
> Hi, the CodeDeploy plugin allows yo
Don't know why that mirror isn't up to date. But the source is OK seems
like: https://updates.jenkins-ci.org/current/update-center.json
2016-01-07 19:53 GMT+01:00 pallen :
> Hi Guys,
>
> The P4 Plugin 1.3.5 release was submitted yesterday, but does not seem to
> have reached the Update Centre?
>
It does not help. I pushed this attempt to use mock-server 3.10.1 to:
https://github.com/jenkinsci/http-request-plugin/compare/master...martinda:feature/use-mock-server-3.10.1
Maybe my pom.xml is wrong?
On Thursday, January 7, 2016 at 11:35:07 AM UTC-5, Daniel Anechitoaie wrote:
>
> It's not on G
On Wed, Jan 6, 2016 at 4:40 PM, Christopher Orr wrote:
> PRs opened in the future should be
> reviewed and merged within a certain time period (1 month?), otherwise
> they should get the "proposed-for-close" label
I do not like the idea of closing a PR merely because no reviewers
have gotten to i
On Thu, Jan 7, 2016 at 3:16 PM, Gavin wrote:
> I'm getting ready to merge and do a release and realized a code review from
> credentials experts might be a good plan.
Stephen Connolly would be the best person to ask.
--
You received this message because you are subscribed to the Google Groups
El 7/1/2016 9:37 p. m., "Jesse Glick" escribió:
>
> On Wed, Jan 6, 2016 at 4:40 PM, Christopher Orr wrote:
> > PRs opened in the future should be
> > reviewed and merged within a certain time period (1 month?), otherwise
> > they should get the "proposed-for-close" label
>
> I do not like the ide
On 07/01/16 21:37, Jesse Glick wrote:
> On Wed, Jan 6, 2016 at 4:40 PM, Christopher Orr wrote:
>> PRs opened in the future should be
>> reviewed and merged within a certain time period (1 month?), otherwise
>> they should get the "proposed-for-close" label
>
> I do not like the idea of closing a
So I published pipeline-editor to the experimental update center repo (via
using "alpha") as
per https://jenkins-ci.org/blog/2013/09/23/experimental-plugins-update-center/
However it doesn't seem to be showing up. I have created a plugin wiki
entry for
it: https://wiki.jenkins-ci.org/display/J
Hey,
On 08/01/16 01:36, Michael Neale wrote:
> So I published pipeline-editor to the experimental update center repo
> (via using "alpha") as
> per https://jenkins-ci.org/blog/2013/09/23/experimental-plugins-update-center/
>
> However it doesn't seem to be showing up. I have created a plugin wiki
Ah! Yes my fault. Being a wiki I copy and pasted an existing one (rookie
mistake, creating a subpage by default).
Thanks so much Chris! I owe you a coffee!
On Friday, January 8, 2016 at 11:53:47 AM UTC+11, Christopher wrote:
>
> Hey,
>
> On 08/01/16 01:36, Michael Neale wrote:
> > So I publis
I getting the similar error with MAven version 3.0.4 & 3.2 as well
INFO] Building war: Test.war
[WARNING] Warning: selected war files include a WEB-INF/web.xml which will
be ignored (webxml attribute is missing from war task, or ignoreWebxml
attribute is specified as 'true')
[pool-1-thread-1 for
Hi,
I tried to release a new version (1.2.1) of the mqtt-notification-plugin
(https://github.com/gdubya/mqtt-notification-plugin).
The release appeared to be successful and shows up on Github here:
https://github.com/jenkinsci/mqtt-notification-plugin/releases
But it is not available via Jenki
24 matches
Mail list logo
