Home → Suggestions →

Upload Publish Profile to create environment

• Edit

sbosell

03 Jun, 2017 01:21 AM

I have 3 suggestions for environments:

• Allow the uploading a of a publish profile file (ie what is exported from an azure web app) in order to create a new environment. Yes, it is kind of a lazy request but I've setup over 75 environments and it would make it so much simpler.

• Please give us some ability to organize them. Tags like projects or something.

• New permission on environment that locks an environment to a project so that when on the project deploy section I don't see ALL of the environments that don't have a permission set. This is kind of annoying every time I go to deploy and I see a list of older environments (probably pre dated the permission but I don't recall).

Thanks for the great tool.

1. 1 Posted by Ilya Finkelshte... on 03 Jun, 2017 11:37 AM

   

   Thank you for your suggestions! We plan to do a lot of improvements in deployment area this year. Please see my comments on your suggestions:

   • Please watch this issue

   • Please watch this issue

   • You can restrict Environment to specific project (under Settings > Project) and then other projects will not see that environment under Deployments tab.

   • Edit

2. 2 Posted by sbosell on 03 Jun, 2017 03:36 PM

   

   Thank you Illya. Your response to item #3 is not what I meant. Let me
   demonstrate what happens:

   Environment set to Project Only per your instruction:
   https://db.tt/Ox6Qv0ALk4

   Here is the project: https://db.tt/i9RKl2Ewu8

   The issue is on the project itself, the deploy is NOT limited to the
   environment, but the environment is limited to the project. My third point
   was to have some kind of way to indicate that the "Only projects" selected
   would set some flag on those projects as well to only allow them to be
   deployed to those environments. Appveyor did one side (environments) but
   not the other (projects).

   In summary, when on the environment screen a checkbox could be added that
   says, "Limit project deployments" and when checked it will only allow the
   projects (screen 2) to see those environment. Consequently it needs to be
   a setting on the project side as well which is missing but I feel it should
   be settable in both areas. I can mock it up if this isn't clear.

   Regards,

   SAM BOSELL
   512.961.1636 mb
   512.686.3016 of/fax
   +51.991813883 mb peru
   ______________________

   3555 Ranch Road 620 S, ATX 78734
   pmgaustin.com

   Av. Paseo de la Republica 3127, Of 301, San Isidro
   Lima, Peru
   pmglima.com <http://pmgaustin.com/>

   • Edit

3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:17 AM.