# New containers (e.g. Trusty/14.04): test on a specific branch?

**URL:** <https://discuss.circleci.com/t/new-containers-e-g-trusty-14-04-test-on-a-specific-branch/3034>\
**Category:** Build Environment\
**Tags:** trusty, container-image\
**Created:** [March 30, 2016, 8:50pm UTC](https://discuss.circleci.com/t/new-containers-e-g-trusty-14-04-test-on-a-specific-branch/3034 "2016-03-30T20:50:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asiebert](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/asiebert/32/1373_2.png) [@asiebert](https://discuss.circleci.com/u/asiebert)\
**Post date:** [March 30, 2016, 8:50pm UTC](https://discuss.circleci.com/t/new-containers-e-g-trusty-14-04-test-on-a-specific-branch/3034/1 "2016-03-30T20:50:07Z")

</div>

We’ve switched to Ubuntu 14.04 for a couple small projects, which was pretty straightforward thanks to the “experimental settings” page.  
We have one bigger project though, which switch is less straightforward due to all the changes, and much harder to test: as the setting is per-project, I had to clone the project in Github and test on the new one, which was pretty cumbersome.

During the last “CircleCi office hours”, we discussed containers, and it sounded like the team was planning on rolling out new containers more frequently in the future. If that’s the case, a straightforward mechanism to test them should be useful − what about:

- being able to flag a specific branch to use a given container,
- and/or to be able to specify the container to use upon launching a parameterized build?

The first would be more convenient to use (push & test & iterate), albeit probably needs more development.

---

<div class="post-metadata">

**Author:** ![sgringwe](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@sgringwe](https://discuss.circleci.com/u/sgringwe)\
**Post date:** [March 31, 2016, 1:32am UTC](https://discuss.circleci.com/t/new-containers-e-g-trusty-14-04-test-on-a-specific-branch/3034/2 "2016-03-31T01:32:04Z")

</div>

I’d also like the ability to flag a branch as a specific container (maybe in the circle.yml) to run a branch on new container while the kinks are worked out.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:38am UTC](https://discuss.circleci.com/t/new-containers-e-g-trusty-14-04-test-on-a-specific-branch/3034/3 "2018-06-18T11:38:08Z")

</div>

Closed on June 18, 2018, 11:38am UTC