Re: ERROR:‘**/*.apk’ doesn’t match anything: ‘**’ exists but not ‘**/*.apk’

[Richard Mortimer]

Hi,

On 16/02/2015 10:17, Prasanth .K wrote:
 while i give extension as **/*.apk in the *Archiving artifacts* it will
 shows error like this ***/*.apk’ doesn’t match anything: ‘**’ exists
 but not ‘**/*.apk*.How can i solve this.any one suggest me.
I think this issue is more appropriate for the jenkinsci-users list. It
doesn't look like a problem with jenkins to me.

That said...

The error is telling you that there are no files ending in .apk in your
build output.

 *-dex*:
   [dex] input: C:\Users\Prasanth\.jenkins\workspace\Test\bin\classes
   [dex] input: 
 C:\Users\Prasanth\.jenkins\workspace\Test\libs\android-support-v4.jar
   [dex] Pre-Dexing 
 C:\Users\Prasanth\.jenkins\workspace\Test\libs\android-support-v4.jar - 
 android-support-v4-3d55c3f91b679ed0ef61b096555c27e9.jar
[dx] 'reg' is not recognized as an internal or external command,
[dx] operable program or batch file.
 
 BUILD FAILED
 C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk\tools\ant\build.xml:892:
  The following error occurred while executing this line:
 C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk\tools\ant\build.xml:894:
  The following error occurred while executing this line:
 C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk\tools\ant\build.xml:906:
  The following error occurred while executing this line:
 C:\Users\Prasanth\AppData\Local\Android\sdk\android-sdk\tools\ant\build.xml:283:
  null returned: 255
 
 Total time: 1 second
 Build step 'Invoke Ant' marked build as failure
 Archiving artifacts
 Finished: FAILURE

The above says your build failed. I suspect that if you fix the problem
with your build failure it will create a .apk file and make everything work.

Regards

Richard

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/54E1C5DF.1000608%40oldelvet.org.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Discussion: Refactoring of JENKINS project in JIRA

[Richard Mortimer]

Hi,

On 04/09/2014 13:22, Tom Fennelly wrote:

At yesterdays governance meeting on #jenkins we talked about configuring
JIRA to provide some helpful text wrt the Components and Labels
fields to help people file issues more consistently.  We talked about
doing it using Javascript hacks.

I installed a trial JIRA and was able to configure the fields easily
enough.  I moved the Components and Labels fields together on the
form and configured some bright ( ;) ) help text on each field.

  * Here's a screenshot of what it can look like

https://www.dropbox.com/s/kn7mc5qzyk9gfwn/Screenshot%202014-09-04%2013.04.05.png?dl=0.
  * Here's the JIRA: https://issues.jenkins-ci.org/browse/INFRA-123


Looks good to me.


Possible text edits aside, I think this should help.


Along similar lines...

Is it possible to add some text to remind people that JIRA is intended 
for reporting bugs and rfes. There is a steady stream of people who seem 
to report their setup/configuration questions in JIRA rather than asking 
via email or IRC.


Maybe add some text to the Issue Type field along the following lines to 
point people at the proper support forums:


Important: This issue tracker is intended to track bugs and 
enhancements to Jenkins. Questions regarding configuration and operation 
of Jenkins should be directed towards jenkinsci-us...@googlegroups.com 
or the #jenkins channel (http://jenkins-ci.org/content/chat) on IRC.


Regards

Richard


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.