In petrel software, can workflow editor be used to automize the use of a "process" such as "geomechanical modeling" on a series of (pre-defined) realizations?
Yes. It can. You have access to all processes from within workflow editor. once you insert the process of interest you can open it just like you do normally outside of the workflow interface, and then define the settings you want. Note that you can define variables in advance and use them as values inside the process.
Related
I would like to know if it is possible to customize the release management interface for on-premise TFS 2017? I would like to put some controls like combo boxes, pick lists, etc. on the UI to codify user selections rather than have free form text entered by the user.
I assume you mean tasks in release definition, you can custom build/release task through extension, more information, you can refer to Add a build task (apply to TFS2017).
If you mean the general boxes in release definition, no you can’t custom.
I have a release definition setup with several tasks. When a developer wants to create a release from this definition, i'd like to give them the option of selecting which features they'd like to release (turn on/off tasks). Ideally this would be via the Create Release dialog using a variable or similar.
Can this be done? Or is the only way to achieve this to create a draft release and enable/disable the tasks on each environment? Believe this is prone to error (toggle task on one environment but forget to on another) and this is not an option as administrator has locked editing of definitions (prevent incorrect setup of production releases).
Understand I can create separate release definitions to cover the options but it seems like a lot of duplication.
Unfortunately, this is not supported in TFS currently. The workarounds are just like you mentioned above, to disable and enable those steps or use draft release.
This is a user voice about your request you could vote:
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/19165690-select-steps-when-create-release
I want to use "Multi level Multi select" feature in "extended choice parameter" in Jenkins configuration. But my properties file is in gitlab. How can I use it?
Is there any other alternative way apart from placing my properties file in Jenkins server?
My purpose is to create a small file with list of deployment objects and control which objects to deploy and which objects not to at different levels. Could you please help.
Here is an example of what I have today:
And it remains the same regardless of the value passed to the Verbosity parameter.
Is there a way to reduce this clutter?
We are using TFS 2015.
In a build process that is based on the Default Template or the Upgrade Template, you can use the Logging Verbosity build process parameter to manage the verbosity of the information that is logged and stored.
The following table lists the Logging Verbosity values and their corresponding effects:
More details please refer this link: Manage Build Information and Control Verbosity
If you are using a custom build template. Suggest you to use minimal Verbosity When Designing a Custom Build Process Template
Users of your build process rely on verbosity filtering to reduce information overload. You can help make this filtering more effective by taking the following measures: Best Practice: Set Verbosity as Low as Possible
These are basically the targets that MSBuild compiles, and as I experienced, it cannot really be controlled with the verbosity.
Our solution was to use custom activity to run the build (we have a wrapper), where we did not pass the TFS logger parameter to the MSBuild.
However in such a case you should consider that the MSBuild task can run for long time, and your custom activity should be cancellable. In this topic I can suggest to read the below article:
https://devtfs.wordpress.com/2013/09/24/dealing-with-long-running-activities/
You may also want to show the compiled targets somehow, therefore you might need to write your own custom MSBuild Logger and a UI to show the result as well.
I am unable to figure out how to change default build/compile settings. The little default checkbox in the lower left of the project options dialog is gone. The documentation states:
The Default checkbox that appeared at the lower edge of many Project Options pages has been removed from the product. If you want to specify options as the default for multiple projects, the suggested alternative is to use option sets instead.
I'm going round and round about "Options Sets", "Configuration Manager" etc.. Is this even possible? What does "specifying options as the default for multiple projects" mean? If I have multiple projects then that means those projects and their options exists, how can I set a default value to something already set? What about new projects?
That feature really has gone and there is nothing like it any more in the product, to the very best of my knowledge. I think the best you can do is as follows:
Create a new project.
Change the project settings to whatever you want them to be.
Change anything else in the default project that you don't like, for example { Private declarations }.
Add this project to the repository.
use File | New | Customize to move this project template onto the File | New menu for easy access.
Project->Options->Target. You can set up a base configuration, and then provide different options that differ from the base for Debug and Release. You can also create custom option sets, which means that they're different from the standard Debug and Release. You can also have different configurations based on different targets (VCL app's Debug build has different options than a FMX app's Debug build, etc.)
To change the default options first starts with defining "default". You can start as low as the "base configuration" through Project->Options->Delphi Compiler, and then choosing the All Configuration target. You can refine it somewhat by altering the base configuration for the Debug and Release configurations. You can also define your own option sets, using the Save button next to the Target list.
Your specific question about "specifying options as the default for multiple projects" means is the base configuration. From there, you refine those base options to give you debug settings and release settings (which can also be saved as your initial defaults, and refined on a per-project basis).
So, for a specific answer, you can change the default by modifying the base configuration, or by getting more specific by modifying the debug or release configurations that inherit from that base, depending on what your end result needs to be and what you're trying to accomplish.