Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7353

Modify AVD names to include Hudson project

    XMLWordPrintable

Details

    Description

      The automatic AVD creation feature is great, but it will only work for a single Android project. Since the AVDs are named based on the characteristics (screen res, etc.) it is likely that two different Android projects will collide on the same AVD. This could be quite problematic when either (or both) projects have the "Reset emulator state at start-up" setting enabled. I believe this should be easily overcome by adding a Hudson project name element to the AVD name.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          orrc Christopher Orr added a comment -

          I'd rather not have numerous duplicate AVDs lying around.

          I do encounter the same problem you mention here so, as per the wiki page, I'd like the next version to have "Automatic locking of AVDs per-slave, so two jobs can't try (and fail) to use the same AVD at once".

          Hopefully I can get this implemented soon.

          orrc Christopher Orr added a comment - I'd rather not have numerous duplicate AVDs lying around. I do encounter the same problem you mention here so, as per the wiki page, I'd like the next version to have "Automatic locking of AVDs per-slave, so two jobs can't try (and fail) to use the same AVD at once". Hopefully I can get this implemented soon.
          jtharp jtharp added a comment -

          In that case, could you make including the Hudson project name a simple configuration setting? I don't mind having the extra AVD directories lying about and it would prevent build contending with the same resource. Besides, it would seem a simpler thing to implement, perhaps allowing it to get done sooner

          Thanks for a great tool!

          jtharp jtharp added a comment - In that case, could you make including the Hudson project name a simple configuration setting? I don't mind having the extra AVD directories lying about and it would prevent build contending with the same resource. Besides, it would seem a simpler thing to implement, perhaps allowing it to get done sooner Thanks for a great tool!
          orrc Christopher Orr added a comment -

          Better late than never...

          I managed to implement this feature. I couldn't find a way to do it, but with some guidance from Mr Jenkins himself recently, it's now done.

          I will make a new release soon once I've fixed a few small issues, things are stable and perhaps when I have another feature ready.

          I've been testing this feature and it seems to be fairly stable at preventing two jobs using the AVD at once.

          In case you're interested in trying it now, I've attached a build with the feature enabled. Only one AVD of the same configuration should ever run on a given computer – other jobs which need the same AVD config will remain in the queue until the first job is finished.

          orrc Christopher Orr added a comment - Better late than never... I managed to implement this feature. I couldn't find a way to do it, but with some guidance from Mr Jenkins himself recently, it's now done. I will make a new release soon once I've fixed a few small issues, things are stable and perhaps when I have another feature ready. I've been testing this feature and it seems to be fairly stable at preventing two jobs using the AVD at once. In case you're interested in trying it now, I've attached a build with the feature enabled. Only one AVD of the same configuration should ever run on a given computer – other jobs which need the same AVD config will remain in the queue until the first job is finished.
          orrc Christopher Orr added a comment -

          Everything has been sorted and this is now released as part of version 1.14.

          Multiple jobs which require the same AVD configuration will not be allowed to start on the same machine in parallel.

          orrc Christopher Orr added a comment - Everything has been sorted and this is now released as part of version 1.14. Multiple jobs which require the same AVD configuration will not be allowed to start on the same machine in parallel.

          People

            orrc Christopher Orr
            jtharp jtharp
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: