Trigger - Tenant not working?

Hey, im really happy that you guys added the whole tenant thing, it makes it possible to nuke a whole shitload of custommade scripts and hacks, however im wondering, i can trigger a deployment to en environment and such, but I can’t seem to trigger deployment against a tenant-tag?

I imagine that its a simple thing to add, but I think more than me would need that feature avalible.

Hi Mads,
I’m glad to hear that you have taken a dive into the multi-tenancy feature in Octopus Deploy 3.4.0-beta01. Sounds like you can already see its potential to simplify your deployment process which is great news and just as we had hoped :slight_smile: .

With regards to your request to trigger a deployment based on a tenant-tag, could you please clarify what you are after? Have you noticed that on the deployment page you can now select Deploy to one or more Tenants and actually select a set of tags? (see screenshot attached). With this approach you can select the tags that you want to match against tenants to be deployed. You should see the number of tenants that match in the bottom right hand corner of the control and when you click Use selected tenants it will show the ones that will be deployed to.

If I have misunderstood what you are after then could you please clarify what you were referring to. Perhaps we have missed an important feature or our documentation might be lacking.

I look forward to your reply,
Cheers,
Rob

Hey rob. I tried to capture this in this screenshot.

Basicly what I want is the trigger to automaticly deploy new versions to the environment as soon as a new release version becomes avalible. So say im currently running service version 1.1.0 when I release 1.1.1 I want it to auto deploy to all my tenants. So I want my trigger to include the tenant option.

Heres how my picture looks now (see attached)

GeoEnviron Hosting:
Gør din hverdag lettere - slip for bekymringer om oppetid, overvågning, og patching. Flyt ind i Geokons moderne hostingscenter, og få automatisk opdateret: databaser, services, programmer, integrationer – ja giv din IT afdeling luft til at fokusere på alle de andre vigtige opgaver, og lad os tage os af jeres GeoEnviron system.

Med venlig hilsen

Mads Klausen
Deployment og Hosting ansvarlig

Geokon A/S
Rødovrevej 11
2610 Rødovre

Telefon: 36 72 30 11
Direkte: 36 36 29 10
Email: mk@geokon.dkmailto:mk@geokon.dk

[http://www.geokondata.dk/support/logo.jpg]http://www.geokon.dk/

www.geokon.dkhttp://www.geokon.dk/
CVR nr: 15959177

And to add to the previous mail. If I add another tenant, and it fits my pattern it will deploy that tanant right away… ofcause.

GeoEnviron Hosting:
Gør din hverdag lettere - slip for bekymringer om oppetid, overvågning, og patching. Flyt ind i Geokons moderne hostingscenter, og få automatisk opdateret: databaser, services, programmer, integrationer – ja giv din IT afdeling luft til at fokusere på alle de andre vigtige opgaver, og lad os tage os af jeres GeoEnviron system.

Med venlig hilsen

Mads Klausen
Deployment og Hosting ansvarlig

Geokon A/S
Rødovrevej 11
2610 Rødovre

Telefon: 36 72 30 11
Direkte: 36 36 29 10
Email: mk@geokon.dkmailto:mk@geokon.dk

[http://www.geokondata.dk/support/logo.jpg]http://www.geokon.dk/

www.geokon.dkhttp://www.geokon.dk/
CVR nr: 15959177

Hi Mads,
Thanks for the additional screenshot, I can now see that you are referring to the new auto-deploy feature in 3.4 triggered by machines. As you can see on that screen, those triggers are machine-based triggers and will only fire when a “new deployment target becomes available”. This means that when a machine is added to Octopus Deploy or the environment is changed, then the trigger will fire. When triggered it will evaluate which releases should get deployed, based on the environment and tenant. It doesn’t trigger when a new release is created. What you may be after is the configuration on the Lifecycle where you can trigger a deployment automatically as soon as a release enters the deployment phase.
I hope this clarifies some things for you. The key to remember is that the project triggers page currently only supports reacting to machine-based events. The auto deployment functionality you are looking for is a lifecycle feature that has been in Octopus Deploy for some time.
Let me know if you need any further help.
Cheers,
Robert

Hi Rob.

I’v used octopus for quite a while, and I know that It’s a “new machine -> then deploy” feature. But what I want to achive is “new tanant (gets tanant tag: “TEST”) -> TRIGGER deployment of latest released code against tanant tag: “TEST”.

Now, I know this is not something I can do in pipelines (im pretty sure) so let me know if you follow. Do I have any possible way to get there?

GeoEnviron Hosting:
Gør din hverdag lettere - slip for bekymringer om oppetid, overvågning, og patching. Flyt ind i Geokons moderne hostingscenter, og få automatisk opdateret: databaser, services, programmer, integrationer – ja giv din IT afdeling luft til at fokusere på alle de andre vigtige opgaver, og lad os tage os af jeres GeoEnviron system.

Med venlig hilsen

Mads Klausen
Deployment og Hosting ansvarlig

Geokon A/S
Rødovrevej 11
2610 Rødovre

Telefon: 36 72 30 11
Direkte: 36 36 29 10
Email: mk@geokon.dkmailto:mk@geokon.dk

[http://www.geokondata.dk/support/logo.jpg]http://www.geokon.dk/

www.geokon.dkhttp://www.geokon.dk/
CVR nr: 15959177

Hi Mads,
The “new machine -> auto deploy release” feature that you seem to be aware of has just been implemented in 3.4 and unfortunately that has not been extended to triggers based on tenants. If you add a tenant or a tag to a machine then it should trigger the machine changed event which in turn will deploy for any related tenants but only because it is the target that has changed, not the tenant itself.
Triggers are a fairly new concept so we may find that users have some other ideas on how they would like it to work or additional triggers. Its definitely something that will continue to evolve as we keep getting user feedback. Feel free to add your suggestion to userVoice and if it seems like an idea that other users want then it might get prioritised for a future release.
Thanks again for your post.
Cheers,
Robert