* update 2 *
The WIKI page is up with the plugin-notifier tag and the same template as
other plugins.
Thanks
--
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 email
update 2 *
The WIKI page is up with the plugin-notifier tag and the same template as
other plugins. https://wiki.jenkins-ci.org/display/JENKINS/Ironmq+Notifier
Thanks
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from
Hi,
Even if we don't skip tests and hand over the package (hpi) as it is, still
gives the exception while installation of the plugin.
hudson.ExtensionFinder$Sezpoz scout
WARNING: Failed to scout com.mobilecloud.project.MobileCloudProject
java.lang.InstantiationException:
Created https://github.com/jenkinsci/ironmq-notifier-plugin
Welcome aboard!
Ulli
Am 03.10.2013 um 08:40 schrieb Mike Caspar mikecanbefo...@gmail.com:
update 2 *
The WIKI page is up with the plugin-notifier tag and the same template as
other plugins.
One way to get all the case results is to iterate all the SuiteResults and
collect CaseResults from them:
ListCaseResult allCaseResults = new ArrayListCaseResult();
for (SuiteResult suiteResult : testResult.getSuites()) {
allCaseResults.addAll(suiteResult.getCases());
}
On Thursday,
Hi,
I have finished backporting issues for 1.509.4. On governance meeting, we
agreed that this is the very last minor release based on 1.509. We have 5
blockers and 8 critical fixes backported, 35 issues in total[1]. All 4
issues rejected from 1.509.3 will be present in 1.509.4.
Kohsuke,
Allright, things are moving along.
The main wiki is setup at Jenkins, and after some teething pains with a
missing GSON dependency I got things MOSTLY working.
I do have one problem, I'm hoping someone has a quick answer for. (Let me
know if I should start a new post instead).
I can build
On Thu, Oct 3, 2013 at 9:32 AM, Mike Caspar mikecanbefo...@gmail.com wrote:
[ERROR] Unresolveable build extension: Plugin
org.jenkins-ci.tools:maven-hpi-plugin:1.95 or one of its dependencies could
not be resolved: Could not find artifact
org.jenkins-ci.tools:maven-hpi-plugin:jar:1.95 in
Thanks.
It was a dependency from iron.io that I was missing.. now I know why.
Much appreciated.
Mike
-Original Message-
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com]
On Behalf Of Jesse Glick
Sent: October-03-13 12:41 PM
To: jenkinsci-dev@googlegroups.com
Hi, thanks for the answers.
I also think that to convert the output to an existing format is the best
option.
If someone wants to develop this project together, contact me, please.
Thanks.
2013/10/2 Samuel Nobs samuel.n...@taitradio.com
another approach would be to re-format lunatest's output
Re Git, you only need SCM polling ticked - you don't need to actually have
a value in the polling field.
Not sure if that helps but thought I'd mention it.
Richard
On Thursday, September 26, 2013, Sascha Vogt wrote:
Hi all,
We are currently in the unfortunate situation that we have multiple
Hi Stephen,
Is the literate plugin going to be the only route into the multi-branch job?
Reason being for enterprisy software we need to enforce things in a
build/release so I can't let my users run abitrary maven invocations that
change the build (and make it unreproduceable).
e.g. they
Den 2. okt. 2013 22.53 skrev pmaccamp pmacc...@yahoo.com følgende:
Been a year since I wrote this, but I have renewed interest so I thought I
would bump. I haven't looked at the source recently so the details may be
outdated. Any advice or mention of other plugins that may have sprung up
eep in mind that not all test results are of the junit type. You may be able
to get all this information with the test.* classes
GetFailedTests is broken so you would likely want to getResult and take Avon
depending on the type if object returned
--
You received this message because you are
Today, many complex plugins suffer from a massive constructor annotated
with @DataBoundConstructor.
This is because the form data-binding requires that all the parameters
passed in through the constructor. See xcode plugin [1] for an example of
this. The situation was worse with plugins that are
Yeah !!! +1000. Thx for this improvement.
—
Sent from Mailbox for iPhone
On Fri, Oct 4, 2013 at 1:46 AM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
Today, many complex plugins suffer from a massive constructor annotated
with @DataBoundConstructor.
This is because the form data-binding
All seems to up and running..
Thanks to everyone who helped out :-
--
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 email
to
Hi all,
I ran into an issue recently in which the git client would exit with status
1, causing the build to fail, even though it successfully checked out the
repo. I submitted a PR with a fix, but I'd like to have someone review it
before it gets merged.
This is great, I was just lamenting this! Now I just need it to be in an
LTS ;-)
On Thu, Oct 3, 2013 at 4:58 PM, Arnaud Héritier aherit...@gmail.com wrote:
Yeah !!! +1000. Thx for this improvement.
—
Sent from Mailbox https://www.dropbox.com/mailbox for iPhone
On Fri, Oct 4, 2013 at 1:46
19 matches
Mail list logo
