How can I make Xcode automatically build when I save changes to a file?
I may have to stop developing for apple if I need to hit that stupid play button/ reach for a mouse one more time.
I am so desperate that I have even considered using Java.robots to click the screen for me on git commits
Look at Jenkins - This does exactly what you want. It's a bit of a faff to get it set up the first time, but it will save you hours in the long term.
You can build without running by hitting (CMD+B) by default. The default behavior of the IDE is to save modified files upon build, so if you just want to save and build all the time, just hit build, and it will do both for you.
You can even modify the shortcut key for build to be cmd+s if you really want to by opening up XCode preferences (Cmd+, by default, or going to the "XCode" menu in the top left and selecting preferences), and go to the keybindings section and change the "Build" action keybinding to be cmd+s
Related
The only way I found to edit an intent in Amazon Lex is by selecting Latest in the drop down menu next to the intent name. Then, every time I click Build, the version number increases. When it reaches the version 7, the Latest option disappears and I am not able to edit the intent anymore. Does it mean I can only edit an intent 7 times? Or is there any other way to edit intents?
Thx
I have successfully updated beyond 7 versions. If you are still seeing this behavior, it may be appropriate to file a bug report.
Are you positive you are saving changes made to your intent, before you attempt to build a new version? Sometimes with the UI it is tricky to know if you have made changes. For example, when adding a slot, you need to click on the "+" button for the new slot to be registered as a change for when you save the intent.
Im not sure this is the right place for this but I need an answer - in the past I have always saved backups (so I can revert back if I break something) of my Xcode projects by copy-pasting the project folder with the project tests/files inside (image below) and naming it a new version (i,e Project 1, project 2, so on):
This has worked well and in the past Ive been able to simply delete a screwed up version and open a past one and the code will be as I left it.
I have now started incorporating pods into my project so I am using the workspace instead of the Xcode project. This now brings in the issue of build "schemes" which appear in the upper left corner.
Not always, but sometimes after copy-pasting I will go back to a previous version and the code has "carried over" from the latest version/scheme. I don't really understand what a scheme is or if this is the problem but it has caused major problems at times.
When using the workspace, how does one properly save backups/new versions to go back to?
It sounds like you need a source control tool, the most used Source Control Management tool is called git. It's what a lot of people use, and you may have heard of GitHub - which is centered around git.
I'd recommend starting by going through this website: https://try.github.io/
As others have mentioned, you should definitely get acquainted with git. And the good news is that about a year after this question was asked, with the release of Xcode 9 (and with all subsequent versions since then), git is built right into Xcode. When you create a project, on the screen where you select the folder you would like to save the project to, you will see a check box, as in this screenshot:
Always enable this (i.e., check the box), and you will never again need to manually save versions of your project to separate folders, as you outlined.
Cheers!
How can TFS be configured to select by default the two checkboxes "Overwrite writeable files that are not checked out" and "Overwrite all files even if the local version matches the specified version" when doing a Get Specific Version?
I am using TFS 2013. My real goal is to automate the process of right clicking a folder, selecting Advanced, and then clicking the two checkboxes. I have created a keyboard shortcut to pull up the window for Get Specific version, but I also want to have the two checkboxes selected by default. I do not want this scripted through the command line as I still want to have the window popped up and manually perform the final step to hit the Get button. Ideally the whole process would work something like Alt-G to pull up the Get Specific Version window, and then manually hit the Get button to complete the action.
There is not option to change this default setting. Even though you don't want to use command, it seems using command line is the only way to automate the process.
tf get-overwrite
tf get-force
https://msdn.microsoft.com/en-us/library/fx7sdeyf(v=vs.120).aspx
I've used the Simple Promote Plugin in Jenkins and it set my build to "keep this build forever".
Is there any way I can delete it?
I got access to the slave who build it and to the master (tried to find anything related in there but no luck).
I'm not sure whether (or how) the Simple Promote Plugin affects this at all, but can't you just click the button that says "Don't keep this build forever", followed by "Delete"?
When a build is marked as "keep forever" (and the padlock icon shows next to the build), you should be able to "unlock" it by pressing that "Don't keep..." button on the build page.
Just as Christopher said, you can remove the build just by deleting the build directory on the master, inside the job directory.
However if you access the page again, the build data gets dumped to disk again. So you either shut down Hudson first, or you go to the Hudson management console and 'Reload Configuration from Disk' which basically discards whatever's in memory and reloads from your config files.
Just make sure you do it right after deleting the folder.
In order to delete builds marked "keep this forever" you should change that flag to opposite state.
Please follow next steps
Open within a text editor $HUDSON_HOME/jobs/job-name/builds/xx/build.xml
Change
<keepLog>true</keepLog> to <keepLog>false</keepLog>
Go to Manage Jenkins -> Reload Configuration from Disk
After these steps you will be able to delete build marked as "keep this forever"
I think that the final (and may be the only one step) to completely delete build from Hudson's history is to modify "nextBuildNumber" file placed in job directory.
Please remember that "Don't keep this build forever" button will only appear when you enable "Discard Old Builds" inside job configuration. I am not sure if it affects Simple Promote Plugin, but it work in this way with 'Release Plugin'.
MichalT
Not sure about masters and slaves, but there is an answer here that allowed me to delete a build "explicitly marked to be kept".
List all keep-forever builds in Jenkins?
Every time I create a new project in Delphi 2009, it loads up two sets of build settings: Debug and Release. Problem is, the Debug settings are all wrong. It has optimizations on, which makes the debugger lose local variables, and Debug DCUs off, which keeps me from tracing into the VCL.
Is there any way to edit the original template so I don't have to keep changing those two settings every time I create a new project?
Set up the Debug configuration you want using Project|Options, and then check the "Default" button at the lower left of that dialog before saving your changes. That makes those settings the default ones for all new projects.
Note that checking the Default button will not affect existing projects; it only affects new projects you create from that point on.