I want to use a variable defined in a variable group in one of my Release Definitions. I know, that I have to add the group to the definition.
Is it possible to explicitely reference a variable by its group? Just like:
$(MyGroup.myVar)
Background: I have multiple variable groups, all containing a variable with the same name. I wand to distinguish between the variable of group A and the variable of group B.
I'm currently using an on-premise TFS 2017 Update 1.
No, we can't reference a variable by its group directly such as $(MyGroup.myVar) , It's not supported.
You have to set different variables in different variable groups. Then reference them in release definitions. See Variable groups.
If there are the same variables in different linked variable groups. The process will use the variable which set in the first linked group.
Anyway, that's a good idea in release definition practice, I have submitted a user voice for this feature, you can go and vote it up for achieving it in future.
I assume your requirement is to use different variable groups in different environments. If that assumption is accurate, then you can now use environment scoped variable groups to achieve just this. See my answer in another thread for overview: Is there a way to use VSTS Variable Groups per environment?
Related
I have developed a Covid-19 Symptom Whatsapp Chatbot using Twilio. The bot basically asks users questions about key symptoms related to Covid-19.
Based on their answers, the bot has to give the users a summary/conclusion i.e. visit the doctor ASAP or call authorities.
My challenge is how to keep the answers to the questions and use them at the end of the survey in Studio. In normal programming i would keep the answers in variables then at the end check the variables and offer a conclusion. How can i implement this in Twilio Studio?
Twilio maintains the variable state throughput the flow. You can use the Set Variables Widget to consolidate all the variable in one place when you reference them or reference them from the individual widgets where the variables are collected (not so ideal).
Set Variables
You can use the Studio Execution logs, to see the JSON path and how to access the variable using {{liquid syntax}}.
you could easily retrieve the variables by referring to them with the syntax {{widgets.name_of_widget.inbound.body}}
you could send them out in a function widget and place them in parameters by inserting the above syntax as the VALUES, and make calculations there.
you call the parameters by event.KEY
Then you can refer back to them by {{widget.function_name.body}}
I can see it is possible to use a single Environment transaction to work on multiple stores. (I'm also assuming writes are possible too).
The high level api of Entity Stores is very convenient for me, but I could not find a way of sharing Entity Store transactions. Looking at the code, I can see entity stores are actually creating Environment transactions but since these are individual transactions I cannot perform operations across multiple stores and commit/abort a single transaction.
Am I missing something or should I say goodbye to Entity Store apis and fall back to Store API?
I was the one who initially asked that question to which you are referencing.
In Xodus there are three different ways to use it:
- Environments;
- Entity Stores;
- VFS.
I'm using Environments API and all Transactions are created for whole Environment. And as I understood correctly you are using Entity Stores API, so you are able to use only StroreTransaction which is started only for a particular Store and to manipulate its Entities.
So, if you require to share one transaction against multiple stores then you require to switch to Environment API.
Taras
If using Environments API you can access any data in the environment regardless of how many named stores are created in it. In the Environments API, Store is just a named key-value map.
PersistentEntityStore is created atop of Environment. Single physical (disk) location corresponds to both Environment and PersistentEntityStore. Transactions are created against Environment or PersistentEntityStore. No matter which API you use, transactions cannot be shared between instances of Environment and between instances of PersistentEntityStore.
I'm wondering how to assign two users to one task in JIRA. I took over a project that was set up by someone else. The problem is we are doing pair programming and we would like to keep track of time.
I dont think you can not actually assign two users to field assignee as it is built-in field.
You can create new required field e.g. pair-assignee and have pair tracked there. Here is a doc about how to setup a custom field.
By design, this is not possible as such - it's a single value field.
But there are ways around this limitation.
Since a number of people had this question, Atlassian has set up a page for the possible solutions/workarounds.
I would like to customize a Work Item Type in TFS to automatically set the Assignee to a particular role. For example (to compare to another Issue Tracker), in JIRA the default Assignee is the Project Lead (so that any ticket not otherwise assigned, gets automatically assigned to whatever person is designated in the role of Project Lead). Can I do something similar in TFS?
So, I realize that one difference between JIRA and TFS is that TFS doesn't (to my knowledge) have the concept of "Roles". The closest thing to that is "Groups", but unlike Roles, Groups can have multiple people (which may be the restricting factor in this problem). I know how to configure a TFS Work Item so that only a certain Group gets listed in the "Assign To" field, but I would like to go a step farther, if possible, and create a custom Group with just one member (e.g., "Issue Guru") and then set up the work item to get automatically assigned to that person.
I'm trying to replicate the Jira functionality here, and maybe there is just no good way to do it in the TFS framework. Any suggestions?
There's a Step by Step Guide on Ivan Fioravanti's Blog for enabling it.
If you are unfamiliar with customising Work Item Types, have a look at the following links (stolen from Grant Holliday's blog).
I never tried this in production but here is something I tried quickly and it seems like it could work.
You can set the default value to a Group by editing work item template in template editor.
Just select Assigned to field and add a DEFAULT rule like shown in the image below.
This will also require you to create one or more groups (one global or maybe one per project). Once you set this up you won’t have to make any updates in the future but only manage people who are in the groups.
I have TFS2010 and I am wondering, where can I find the global list values within the TFS database. I am trying to find the correct table name and database that contains the values.
Thanks!
We don't support using the operational data store, instead use the API's we provide to you. To start using the API for global list see http://blogs.microsoft.co.il/blogs/shair/archive/2010/03/08/tfs-api-part-23-create-global-list-xml-way.aspx