Job A isn't really setting VAR_REV. Instead, it's setting it in a local
scope (ie it shells out, sets the env var in that shell, then exits the
shell). Try using the Inject Environment Variable plugin.
On Wed, Mar 30, 2016 at 3:52 PM nguyen wrote:
> Hi,
>
> I have two build job *A* and *B*.
> j
https://stackoverflow.com/questions/26026431/how-to-fast-fail-jenkins-build-flow-plugin-job/26026432#26026432
On Mon Nov 10 2014 at 8:35:18 AM Ginga, Dick
wrote:
> Having looked at this again, you should be able to do what you want in
> the shell script itself. I am not an expert here, so I wil
Never mind. All the RV_EXCEPTION_NOT_THROWN warnings had been fixed
between the Jenkins run and my local run.
On Oct 18, 11:22 am, Noel Yap wrote:
> Jenkins FindBugs plugin is reporting instances of
> RV_EXCEPTION_NOT_THROWN, but when I look through the findbugs.xml
> files, there
Jenkins FindBugs plugin is reporting instances of
RV_EXCEPTION_NOT_THROWN, but when I look through the findbugs.xml
files, there's no mention of it (although it does mention other types
of warnings). This is the behavior even if I set reportLevel=low.
Where is this coming from?
Thanks,
Noel
