I'm in the process of creating a formula to submit to homebrew-core and I see the documentation describes the process of creating a bottle. However what's not clear to me is: do I need to create it myself? Or will the system automatically generate and add them to the formula?
However what's not clear to me is: do I need to create it myself?
No, you do not need to create bottles yourself. In fact, you can't; only the Homebrew maintainers can upload bottles.
After your formula has been accepted, BrewTestBot (a bot operated by the Homebrew project) will build bottles if appropriate and add them to the formula automatically. You don't need to do anything special.
Related
Is there a way to limit the number of children that can be created under a parent node in Umbraco, ideally I would like to only allow one?
I am not sure if this can be done either via the CMS or set via code in a config file.
Short answer: no, there's no such functionality built into Umbraco, nor are there options to configure it directly.
Longer answer: you could implement a bit of code that hooks into the Saving event (https://our.umbraco.com/documentation/Reference/Events/ContentService-Events#events). There you could check the number of siblings (or rather if there are siblings at all) of any node that hasn't been saved previously - and cancel further saving if any siblings already exist.
Sounds a bit funny to need that, though. What is the scenario?
This is a valid scenario and depending on your Umbraco version, you can use a package, namely NodeRetrict, to restrict the number of nodes that could be created under a parent node.
Please be aware that this package currently supports some Umbraco v7 versions, but not Umbraco v8 and v9 versions.
If you want to check this package to create your own solution or contribute to this package, please take a look at the source code here.
I'm using TFS 2013 Update 3 and Release Management 2013 with Update 3 (agent-based templates).
In the Release Management client, I'd find very useful the ability to add a comment for any action/component (or even a group of them) that is part of a deployment sequence. This is because often it's obvious what an action/component does (e.g. "Move File or Folder"), but it might be useful to know why that is done, also in the context of that particular deployment sequence.
I haven't found a way to achieve that, is it actually possible?
If not, do you have any alternative solution or do you know if a similar feature is available in newer
versions?
One thing you can try (but I am not sure if Agent-based Update 3 allows it) is to rename the action/component once dropped on the canvas. I know vNext templates allows it, and some earlier versions of Agent-based allowed it (but not the recent one... it seems to be broken).
Another less optimal option would be to add a parameter (which would be ignored during the actual deployment) - call it 'Notes' or similar - and just fill its value with the description of what this action/component does. It is less obvious and you may need to scroll to see it when you have many params, but it would be available. Also, this would only work with custom actions and components.
Last option would be to put your action/component (or group of) inside a 'Sequence'. You can rename those by clicking on the name. That would give some context on what that action(s) does.
I'm attempting to modify my build process file for TFS 2010. I have a flag that is set when queuing the build, and when said flag is set, I want to create a Label, and add all the source files in the compiled project to that label.
On sequential builds, with the flag set, I than want to replace older source files in said label with anything new in the changeset being compiled.
I've been attempting to do this with LabelSources with no luck, and there is but vary poor documentation on either LabelSources or LabelWorkspace (whats the difference?).
Here's what I currently have:
<mtbwa:LabelSources
Child="[LabelChildOption.Replace]"
Comment="Published to Container"
DisplayName="Create Container Label"
sap2010:WorkflowViewState.IdRef="LabelSources_1"
Items="[{"$/Foo/LabelTest/Sandbox/"}]"
Name="[String.Format("{0}-{1}", LabelName, Version_Container)]"
Recursion="[RecursionType.Full]"
Scope="$/Foo"
mva:VisualBasic.Settings="Assembly references and imported namespaces serialized as XML namespaces"
Version="T" />
It definitely hits the action, but no labels can be found after the fact.
Any help would be much appreciated. and Any tangible documentation, other than Class Documentation with sparse definitions would also be greatly appreciated
Edit 1: Tried to clear up my goal.
What you are trying to do is built into the existing template. There should be an option in the process definition that refers to Clean Sources which will be set to True.
This option controls wither the build sources get cleaned, deleted and start afresh. Or if a differential is done.
If you have a lot of source code you can set clean sources to false and save a bunch of time getting the code.
You can also speed the build by placing a TFS Proxy on the build box which will cache the files and make a clean build quicker.
In my experience, Most of the built-in activities are poorly-documented for a reason - their only well-tested use case is their use inside TFS' built-in templates (DefaultTemplate.11.0.xaml, etc.). I'm afraid you're going to have to write some custom code, in the form of a custom activity, powershell script or something, to achieve other goals.
That said, I don't really understand the process you're trying to set up. Do you just want to have a label set as your latest-successfully-built sources? Why not use the one created automatically by the build itself?
I have automatic build numbering setup, based on build date/name, using approach proposed by John Robbins from Wintellect described here. So the version/resource file is automatically created on build time but not checked-in.
I wonder how to approach a problem of rebuilding historical versions (based on labels) and having the original build number/name in them. Is it possible to detect 'GetVersion' parameter of MSBuild and try to recreate the original build name from it?
Is it a sane approach anyway? What alternatives do you see?
It's not easy to build a specific changeset (though possible, if you pass the changeset number into your build script and modify the "Get Latest" portion of the build).
However, one easier way of handling this is to create a branch of your code. You can branch at a specific date or changeset, which will create a copy of code from that point in time. Your build scripts can then be pointed at this code.
With respect to your versioning problem: you may find that the only sensible way to do this is to hardcode the required version number. My understanding of your version numbering strategy is that it doesn't relate to anything you can derive from the source (such as the changeset number, date, or file content), and it isn't checked in - so re-calculating it will be pretty complicated!
You ask question Rebuilding historical builds but it actually Rebuilding historical change Set or label, I know what you mean but I am trying to tell you what I need to say, so I don't see that we need to build a label with the specific name the label or change set can has many build as needed and since we use the date and time in the build number it will more realistic to has the current time and date the build was taken instead of old one
Thanks
M.Radwan
I have an Ab-Initio plan consisting of more than one graphs in it. If the plan failed in one particular graph during its 6th phase, then how can the plan be restarted from the particular graph and that too from the beginning.
Note: Not for the last check point available in the .rec file.
In this case what should i do?
Delete the respective *.rec file from the run directory for the plan it was created. And rerun the graph. As it will not find any recovery file it will execute from the beginning.
One approach would be that you can disable the remaining graphs by selecting them, right click and then select disable. Now when you run your plan, only the enabled process will run without having to rerun the entire process, hope this helps and in case it does, pleas check the tick mark on the left and mark it as a correct answer and upvote.
Abinitio provde excellent first-line support services for their customers. I would recommend you email them support#abinitio.com. From experience it helps if you state your co>op version and your gde version and package the graph in question and send that as well.