Comments
Mitch and Kirk,
We're serious about plugins but the SCM plugin API won't be ready until later in the year. We'll keep the community posted on progress.
--Mark
Hi Simon,
BTW what does TEDP stand for?
Pavan referenced it in his reply:
# If both CI Pipeline and Test Environment Deployement Pipeline (TEDP)
--Mark
As of Go 12.1, Go has native TFS SCM support. Check this out.
--Mark
As of Go 12.1, Go has native TFS SCM support. Check this out.
--Mark
Hi Jebastine,
Instead of using a Go Environment Variable, use a Go Parameter. Give that a go and let us know if that doesn't work.
Thanks.
--Mark
Stephen,
Glad to hear you are using environments.
Since the application status check is already decoupled from your deployments, would it make sense for you to break apart your current pipeline and introduce an additional pipeline (with only one stage) in each Go environment? This would associate the status check with your environment.
You can then use the Environments page to see the results in the context of each environment, or you can view them on the Pipelines page.
If I'm missing something let me know and we'll try to figure out how we can help.
--Mark
Hi Stephen,
Go Environments (enterprise feature) sound like they may be a great fit for your use case.
- You can model each one of your environments as a Go environment, and see each environment on either the Pipelines or Environments page.
- A Go environment is a grouping of pipelines and agents. e.g. a deployment pipeline or in your case a pipeline that checks the status of your app
- A Go environment has a pipeline locking concept to ensure that only a single instance of a pipeline can be run at a time. This comes into play when you use Go to deploy software and you don't want to interfere with an in-progress deployment.
- Go supports pipeline templates. This may come in handy if you see a pattern across your environments.
- Go supports environment variables.
Hope this helps.--MarkIan and Scott,
... and I take Scott's point that an environment has a pipeline, but when you are creating a pipeline the next step typically is for it to be in an environment so it can be used. Therefore you would expect to be able to do this from the same area as setting up the pipeline, in a natural flow. The agents get Environments assigned from the agent page, so why not pipelines from pipeline setup?
Agreed! That's a great point. I've added it to the backlog. Thank you for the feedback.
--Mark
Ian,
There is a UI for this.
On the Environments page, click on the environment name. You'll end up on a page where you can edit your environment's pipelines, agents and environment variables.
We'll need to address the discoverability of this feature (or move environment administration into the Admin section). As always, thanks for the feedback!
--Mark
Hi Josh,
First, I'm happy to hear that you are evaluating Go.
I assume you've already come across the post explaining how to use Go with TFS and SvnBridge.
Direct support for TFS is high in our product backlog and will be coming in the next major release, Go 3.0, which is slated for early 2012.
Hope this helps and let us know if you have any other questions or feedback.
--Mark
Hi Matt,
Ah, sorry about not being clearer!
We released 3.3, fixed the bug I described in my previous reply, and released the fix as part of a new 3.3 installer.
Go to the "About" page (you can find a link on the footer). If it's not this revision you won't have the fix and will need to upgrade.
22842_5b12d0b65efc
If you have uncovered a different bug, please contact our support team.
--Mark
Hi Matt,
We've already fixed a 3.3 issue that had resulted in the display of an innaccurate last login value if the user had the "Remember Me" option checked.
You'll need to get and upgrade to the latest Mingle installer from the download page.
If this is a different problem, please contact our support team.
--Mark
Hello,
We heard your feedback and made the following changes.
- We increased the font size in the properties section on the Card Details page.
- We reduced some of the white space in the properties section on the Card Details page.
Please contact our support group to get your hands on the 3.3 patch.
Keep the feedback coming!
--Mark
Picture 1.png (63KB)