Hi Jeff,
it's a bug introduced in core/maven-plugin a few versions ago. I think I
saw a commit fixing it this week so it will released either with 1.530 or
1.531.
If you are starting with Jenkins, I can only recommend you to install the
LTS version rather than the latest version. This will avoid
On Thursday, August 22, 2013 12:30:21 PM UTC-4, Krishna Gundala wrote:
>
> Hi Jenks,
>
> I need help in integrating my ruby functional test cases to run on Jenkins
> against dev builds.
>
> My project is Maven project and Functional test cases are written in Ruby.
>
> Can any one help on this?
>
I've found that when using the description setter plugin and the regex
matches text in the logs where jenkins would put in a link (say a build #
or a user name) back to another part of jenkins, that the description gets
a lot of junk in it.
For example I matched a build name which jenkins link
I have a new Jenkins installation (1 master + 1 slave so far). I have
about 8 Maven jobs so far. When a build fails, the maven errors aren't
shown, I only see INFO messages, which seems very odd.
If I run the maven command on the jenkins system directly, I see the
errors. In the maven options,
The pull request is now https://github.com/jenkinsci/jenkins/pull/916.
Am Freitag, 23. August 2013 15:41:15 UTC+2 schrieb Stefan Wolf:
>
> Hi,
>
> after trying to use the feature "Aggregate Downstream Test Results", i.e.
> the AggregatedTestResultPublisher, I ran into some problems. The main
> p
Hi,
after trying to use the feature "Aggregate Downstream Test Results", i.e.
the AggregatedTestResultPublisher, I ran into some problems. The main
problem is fixed by my pull
request https://github.com/jenkinsci/jenkins/pull/915, namely that clicking
the "Latest Test Result" link on the Proje
Hi Stephen,
Thanks for the info.
I forgot to mention that the credentials are need to access our SCM tool.
WE use SCM Surround and this tool is using LDAP credentials. Whar I want o
achieveis:
1) ecah Jenkins user has only one plca where to save SCM Surround
credential (i.e. LDAP credentials)
2
Jeff is absolutely right of course. The default mode for "ct setview" is
to spawn a new shell. The only way to use this within Jenkins is to use
the -exec option.
We had a similar situation several years ago. We would actually generate a
script on the fly to do what we needed to do for that
We split up into two jobs to have more control over the pipeline. Some
cases we want to build->lint->test->release. Some cases we may want to
just lint->test. Breaking these up into individual jobs gives you more
control to only do what you want to do. For one team we lint on every
commit,
On 23 August 2013 10:00, Alberto Morando wrote:
> Hi Stephen,
>
> Thanks for the help.
>
Thanks for reporting the issue.
>
> Now I have downloaded the new credentials plug in version (1.7.4) and I
> would like to use the credentials I have saved in the user configuration
> page (I can see that
Hi Stephen,
Thanks for the help.
Now I have downloaded the new credentials plug in version (1.7.4) and I
would like to use the credentials I have saved in the user configuration
page (I can see that now :-)).
I was thinking to use the credentials in all the job that need them. In
this way the pa
'Build with Params' in the plugin. You can see it in the breadcrumb trail in
the plugin screenshot. Here's the corresponding source:
https://github.com/jenkinsci/build-with-parameters-plugin/blob/master/src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction.java#L63
'Bu
12 matches
Mail list logo
